Home/ Questions/Q 8753833
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T13:30:09+00:00

We’re using JQuery AJAX to login. The login service issues a HTTP 302, with

  • 0

We’re using JQuery AJAX to login. The login service issues a HTTP 302, with the location being the GET for the user logged in, or (in the case of a log in failure), a REST endpoint that always returns a not authorized HTTP status. At the same time as the 302, we issue a set cookie for the JSESSIONID. The cookie is a HttpOnly cookie.

When using a straight HTTP form post, the redirect works fine, and everything is set. When using JQuery AJAX, the redirect to the GET /user/{userId} doesn’t work as the cookie is not sent with the second call. This failed second call should trigger yet another redirect to the auth-failed endpoint, but it actually doesn’t. Inspecting it, I see that the second call gets
“canceled”. What does that mean, and how do I fix the problem in the first place?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s possible you are falling foul of the same-origin policy. Is the domain you are logging in to the same one that the page/script file was served from?

    If not you’ll need to use CORS (cross origin resource sharing) to get the cookie to stick.

    You can learn more about it here:

    http://www.html5rocks.com/en/tutorials/cors/

    https://developer.mozilla.org/en-US/docs/HTTP_access_control

    • 0