on 12-12-2014 12:04 PM
Hello,
What could be the reason that each call into the WebI RESTful api delivers a HTTP 404 Not Found?
We have the RESTful url and can connect to the web service.
We see that when the WACS is not running we get a connection refused.
We see that when the WACS is running but disabled the connect call hangs until timeout (after 1+hours).
We think that the HTTP 404 we get with each WebI RESTful call (e.g. URL/raylight/v1/documents/12345678/variables, or links, or properties, or dataproviders ...) has something to do with an installation/configuration issue of the WebI RESTful api.
It does not seem to be an access right problem.
We found many patterns how the WebI RESTful api behaves when the access rights are not sufficient. Neither of them had the HTTP 404 in each call.
How can we prove that the WebI RESTful web services functionality is installed and configured correctly?
So far we checked the settings in the WACS, and the settings in CMC.Applications.RESTful Web Service. The settings there seem to be ok.
What else can we check?
Thanks,
Bernd
Hi Bernd,
You can send a request to:
[GET] http://<server>:6405/biprws/raylight/v1/about
(this call doesn't need authentification)
I don't really understand what is your problem. Is the hanging intermittent?
Best regards,
Anthony
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bern,
Any news?
What about trying to reach from a browser for instance:
http://<yourserver>:6405/biprws/raylight/v1/about
Best regards,
Anthony
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.