This content has been marked as final. Show 5 replies
could it be your Chrome isn't accepting or keeping the login cookie?
If so, is there any chance you could use Firebug or a similar plugin in your Chrome to trace the login?
Thanks for that suggestion. I turned on Inspect Element in Chrome. I can see two cookies under the domain for my app. One is for LOGIN_USERNAME_COOKIE and the value is my username. The other is for WWV_CUSTOM-F_(I assume this is some internal session/app id)_100. I know that 100 is the Apex-assigned ID for my application. Using Firebug in Firefox shows me the same two cookies.
These are the two cookies I'd expect.
Could you compare the "network" part in Chrome and Firefox? The first action would usually be the post to wwv_flow.accept that leads to a redirect (status 302) to f again (generates the main page), followed by various static files referenced from that page.
Or do you have some special (custom) authentication process that would behave differently?
There's no custom authentication.
I used the network tool in both FF and Chrome. In both I see the first two calls to the first two items as you mentioned, and then an additional 25-27 calls to items that produce the page. I noticed that the total number fluctuates between 26 and 29, but I assume that's because the browser cached something and decides not to call it again when I refreshed the page or logged back and redisplayed it.
Hmm, so the authentication itself doesn't seem to be the problem. Is there any difference in the next step? If you do the same clicks in your browsers, the request should be the same, but as they don't show the same result, the Chrome-Request must be different, e.g. it doesn't send all cookies or cuts the URL with your session ID or something.
Do you have any popup or similar in your page that could open a new browser session (and hence a new APEX session)?