The accepted answer does not work for the reasons given. I posted a comment with a link to a question that described a hack to get round the problem of the 302 being transparently handled by the browser: How to manage a redirect request after a jQuery Ajax call However, it is a bit of … Read more
I had the same problem in my app. You can’t really “catch” a 302 redirect response. The browser catches it before Angular get it’s hand on it. so actually, when you do receive your response – it is already too late. The bad news: it’s not a problem in the angular platform. The xmlHttpRequest do … Read more
It shouldn’t be cached at all unless there’s also a Cache-Control or Expires header returned by the web server. According to RFC 2616, section 10.3.3 302 Found The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. … Read more
I had the same problem. Here’s how I solved it. In IIS7, click on your website, then double-click the Authentication button. Click on Anonymous Authentication, then click the Edit… link on the right hand side. Make sure the “Application pool identity” checkbox is checked. My application pool is running under the “Network Service” user (not … Read more
The correct one is 303. I use it and haven’t found any compatibility problems with UAs newer than Netscape 4 (1998, released 17 years ago). If you use 302, you’re risking that UA will re-send POST to the new URL instead of switching to GET. Still, if you’re worried about HTTP/1.0 clients (which don’t support … Read more
For a 302 Found, i.e. a temporary redirect do: header(‘Location: http://www.example.com/home-page.html’); // OR: header(‘Location: http://www.example.com/home-page.html’, true, 302); exit; If you need a permanent redirect, aka: 301 Moved Permanently, do: header(‘Location: http://www.example.com/home-page.html’, true, 301); exit; For more info check the PHP manual for the header function Doc. Also, don’t forget to call exit; when using header(‘Location: … Read more
I don’t know about the 302, but I tested the 301 on some browsers today, here the results: SCENARIO: user clicks link on domainX that points to domainA. domainA does a 301 redirect to domainB. IE8 referer when landing on domainB is: domainX (even when using InPrivate browsing and even when user opens link in … Read more
According to this blog post: http://blog.dubbelboer.com/2012/11/25/302-cookie.html all major browsers, IE (6, 7, 8, 9, 10), FF (17), Safari (6.0.2), Opera (12.11) both on Windows and Mac, set cookies on redirects. This is true for both 301 and 302 redirects. As @Benni noted : https://www.chromium.org/administrators/policy-list-3/cookie-legacy-samesite-policies The SameSite attribute of a cookie specifies whether the cookie should … Read more
A 302 redirect means that the page was temporarily moved, while a 301 means that it was permanently moved. 301s are good for SEO value, while 302s aren’t because 301s instruct clients to forget the value of the original URL, while the 302 keeps the value of the original and can thus potentially reduce the … Read more
cballou’s solution will work if you are using an old version of jquery. In newer versions you can also try: $.ajax({ type: ‘POST’, url:’url.do’, data: formData, success: function(data, textStatus, request){ alert(request.getResponseHeader(‘some_header’)); }, error: function (request, textStatus, errorThrown) { alert(request.getResponseHeader(‘some_header’)); } }); According to docs the XMLHttpRequest object is available as of jQuery 1.4.