I am using Apache Tomcat 9 to run documentum rest APIs from Windows server but whenever I am hitting the API from PyCharm it is giving the 502 error (http response code) and the text is:
**The server you are requesting is not responding. This is not a proxy issue. To solve the problem contact server administrator. Your sending address on the internet is Ip address.
The same APIs are running fine from POSTMAN.
API: http://localhost:8080/dctm-rest/repositories
Please help and suggest how to resolve this http error of 502 when hitting API from PyCharm.
I am trying to access rally data with API key,username and password but getting "HTTP ERROR 401 Problem accessing Reason: Full authentication is required to access this resource Powered by Jetty" issue.
I am using Node Version 10.18,
Can anyone help me in this.
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)
Environment:
Windows Server 2012 R2
JRE 1.8.0_101
IBM WAS Liberty Core 8.5.5.5
IBM MFP 8.1
Apache Web server
We have set up the UAT with the above environment. We have deployed our application on the server, have deployed adapter for user authentication and a resource adapter to fetch the data.
When we invoke an adapter procedure without security (unprotected) the app is fetching the data. But when we try to invoke an adapter procedure with default scope or with a custom scope Instead of triggering the challenge handler, we are getting failure response with error status ‘201’ and error message ‘Created’.
Another observation is that, when the WLAuthorizationManager.ObtainAccessToken is invoked with default scope or with push.mobileclient, it is giving the same failure response with error status ‘201’ and error message ‘Created’. The same application works fine in the development environment.
When I try to obtain a token from postman using https://domain:port/mfp/api/az/v1/token and pass the scope, grant_type and the necessary authorization header, it is providing the valid response with token. But from the app when we try by obtain token it is given failure response.
Failure response
{"status":201,"statusText":"Created","responseText":"","responseHeaders":{"connection":"Keep-Alive","content-language":"en-US","content-length":"0","date":"Fri, 17 May 2019 05:42:45 GMT","keep-alive":"timeout=5, max=100","location":"/mfp/api/registration/clients/1e746550-e804-4ee7-88ba-b99896qqqqpwo","server":"Apache/2.4.39 (Win64) OpenSSL/1.1.1b","via":"1.1 ","x-powered-by":"Servlet/3.0"},"errorMsg":"Created","errorCode":"201"}
201 is not a response code that is expected from the /token endpoint. This is very likely coming from an intermediate element in your topology. You've mentioned about the Apache Web Server as part of the configuration - is this sending the 201 ?
Moreover, the actual response from the server shows "server":"Apache/2.4.39 (Win64) OpenSSL/1.1.1b"
So, here is what you can do
a. Try bypassing the web server and see if resolves the issue - in all likeliness, it should.
b. Validate the configuration settings of the Apache Web server to see why the 201 is being returned.
Late to the party, but for anyone that is still running into this error:
Install the following interim fix: 8.0.0.0-MFPF-IF202006151151
This solved the error for me. Seems to be a bug in MobileFirst, took me ages to find.
Api Auto discovery Error 400... when i deploy my api in cloud(anypoint through runtime manager) it got deployed. but, when i tried to get a response from postman, it says "service not available",i am not able to get a response back from postman.
Is it error 503? In that case the explanation is that the API is not correctly paired to the API in API Manager with client credentials and Autodiscovery. See https://support.mulesoft.com/s/article/API-returns-503-Service-Unavailable-error-to-clients