Skip to content

[ON HOLD] handle HTTP 3xx redirect with Location header #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

[ON HOLD] handle HTTP 3xx redirect with Location header #79

wants to merge 1 commit into from

Conversation

ingoe
Copy link

@ingoe ingoe commented Nov 13, 2012

Intercepts a ajax response with HTTP status 3xx and a Location header and issues a new axaj request to the URL provided in the Location header.

Intercepts a ajax response with HTTP status 3xx and a Location header and issues a new axaj request to the URL provided in the Location header.
@graingert
Copy link

This would be useful but different redirects have different semantics, eg what to to with POST data etc

@jakerella
Copy link
Owner

Our apologies for the delayed response, we're just starting to get back into active development here.

This is an interesting concept, and definitely something we can look at, but there are a number of aspects to 3xx redirection that we would want to handle. For example, 304 codes simply mean the resource was not modified, but it does not preclude the addition of a Location header. Additionally, there is some clean up to do in here, for example, you're using $.ajax(), but we should really be using the aliased _ajax() method. In order to consider this change we would need full tests as well.

Please let us know if we can help!

@jakerella jakerella changed the title handle HTTP 3xx redirect with Location header [ON HOLD] handle HTTP 3xx redirect with Location header Apr 18, 2015
@jakerella
Copy link
Owner

Closing for inactivity, but opening a new issue to address this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants