This content has been marked as final. Show 2 replies
Joszef:1 person found this helpful
I attempted to reproduce the issue you describe but I could not. On a 4.1.1.00.23 instance, I enabled a report for RESTful access on a public page. In a new tab in the same browser, I invoked that report like:
That invocation worked. To attempt to reproduce your scenario, I connected to a remote machine using VNC, started firefox and pasted the same URL from above. The result was a JSON document not a 404.
This feature should not rely on a cookie being set whatsoever. I cannot think of a reason you are experiencing the issue you describe.
Thank you, Jason.
I agree that it should not have anything to do with cookies, but yesterday it seemed so. Today I revisited this problem on my system and it seems much more weird than yesterday.
Actually, I have 2 classic reports on my page enabled for RESTful access.
The first one returns a JSON document regardless that I fetch it from browser or using the command line utility wget from the same host.
The second one returns a JSON document when fetched from browser, anf gives 404 when I fetch using wget.
Is there a way to trace what is going on inside XEXDB?