On production we faced a problem with service worker. We don`t use PWA feature but still have error. Is there way to avoid this?
ERROR: Service worker registration failed with: TypeError: Failed to register a ServiceWorker for scope ('https://********') with script ('https://*****/ngsw-worker.js'): A bad HTTP response code (404) was received when fetching the script.
I think this is really an Angular question, rather than a Spartacus-specific question. See the Angular documentation at https://angular.io/guide/service-worker-devops (particularly the section Service Worker Safety > Fail-safe)
Related
How can I resolve
OAuth2 request failed: Service responded with error: 'Service has been disabled for this account.'
?
I have a Chrome extension that requires a "See, edit, create, and delete all your Google Sheets spreadsheets" sensitive scope. I think maybe some companies block apps with this and this is what is triggering the error.
Do you know if this is the case and how to resolve / maybe do further authentication to remove this error? I was thinking maybe registering on restricted scope .....but honestly not sure if that'll work
I registered sensitive scope but it still seems to be triggering an error for some folks. I think it is a company issue & wondering if others have had this problem and if there's a way to get around this
Whenever I try to add the following endpoint, "http://ws.cdyne.com/phoneverify/phoneverify.asmx", during the Managed API setup process and press the Test button I get an error on the server. ERROR - APIProviderHostObject Error occurred while connecting to backend : "stackOverflow preventing me from showing this link", reason: Connect to ws.cdyne.com:80 timed out
When I try this exact same process on a machine outside of our proxy it works fine. I have gone into the axis2.xml file and added proxy information and even went as far as installing cntlm and setting the proxy to localhost - same error.
I can browse to the above link just fine on this machine.
My environment is Windows 10.
I assume you talk about clicking the Test button when providing Backend Endpoint in API publisher.
The way that Test button works at the moment (as far as I understand) is that it invokes HTTP HEAD method on the endpoint provided (because according to RFC 2616, "This method is often used for testing hypertext links for validity, accessibility, and recent modification.")
Then it checks response. If response is valid or 405 (method not allowed), then the URL is marked as Valid.
Thus sometimes, if backend is not properly following RFC, you might get otherwise working URLs declared as Invalid during the test because of that improper HEAD response evaluation. Obviously, this is just a check for your convenience and you can ignore the check if you know the endpoint works for the methods and resources you need it to work.
So my advice would be to try ignoring the Test and just finishing setting up and publishing the API.
P.S. I am checking it on WSO2 API Cloud but behavior is identical to downloadable API Manager.
Is there any way to get detail exception & Stack trace from deployed Web Api?
Even if I deployed in Debug mode, do I get detail error traces?
I got bellow message from server API
"message": "Processing of the HTTP request resulted in an exception.
Please see the HTTP response returned by the 'Response' property of
this exception for details."
This happened only in server, same code running perfectly in local machine.
Did you check the content-type for the request that you are performing?
Sometimes this error comes because you don't specify this value, e.g. "application/json" in the headers of the request.
If your scenario is to have a central place to log any exceptions that happen when requests are being processed, then I would suggest to take a look at 5.1 version of Web API (released couple of days back), specifically the Global Error Handling feature.
http://www.asp.net/web-api/overview/releases/whats-new-in-aspnet-web-api-21#global-error
If you go to the above page,you should notice ExceptionLoggerContext which gives you details of the exception.
About Web API versions 5.0 and before:
In these versions there was no really a central place for catching exceptions. ExceptionFilterAttributes caught exceptions for only certain areas of Web API.
I have a jsp application deployed on OAS server 10.1.2.0.2. The problem which I have is that only sometimes the application cannot invoked web service method. The error which I get is :
16:58:52,332 INFO HTTPSender:202 - Unable to sendViaPost to url[http://prodbus.farm.globul.bg:8000/BPACommunicationWS/BPACommunicationWS]
org.apache.axis2.AxisFault: Transport error: 401 Error: Authorization Required
at org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:310)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:200)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
The problem is fixed after restart the OC4J instance. Also the allocation of the memory is growing a lot.
Does somebody know the reason of this? I used axis version 1.5.1.
Thanks in advance.
The problem was that I use axis2 for a web service with authorization in ClassOne and in ClassTwo I use axis2 without authoiztion and somehow when I make the authorization in ClassOne axis2 remember that there is a authorization and do it in ClassTwo.
I remove also the set preemptive flag and everything works fine.
I am deployed my published the WCF web service to my server and when i am tryihg to
access it its giving me following error????
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /API/Errors/GeneralError.aspx
It was an application pool issue, on recycling the application pool the issue got resolved.
I would say it has to do with the handlers setup in IIS...
read this http://bloggingabout.net/blogs/jpsmit/archive/2007/01/17/wcf-http-404-when-hosted-in-iis.aspx