Skip to content
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

Handle unencoded Location headers #6

Closed
wants to merge 2 commits into from
Closed

Conversation

mudge
Copy link
Contributor

@mudge mudge commented Apr 24, 2015

GitHub: #4

In production, we've seen a few shorteners return unencoded URIs in their Location headers (contrary to the RFC 7231 specification). We could use URI.escape and URI.unescape to deal with these but they have been deprecated. Instead, bring in the Addressable gem as a dependency to handle normalisation.

This means that Embiggen now returns Addressable::URIs rather than Ruby standard library URIs which is a breaking API change if you rely on URI-specific features (e.g. port which is much stricter with Addressable).

mudge and others added 2 commits April 25, 2015 11:46
GitHub: #4

In production, we've seen a few shorteners return unencoded URIs in
their Location headers (contrary to the RFC 7231 specification). We
could use URI.escape and URI.unescape to deal with these but they have
been deprecated. Instead, bring in the Addressable gem as a dependency
to handle normalisation.

This means that Embiggen now returns Addressable::URIs rather than Ruby
standard library URIs which is a breaking API change if you rely on
URI-specific features (e.g. port which is much stricter with
Addressable).
@mudge
Copy link
Contributor Author

mudge commented Apr 25, 2015

Going to re-open this against the 1.x branch.

@mudge mudge closed this Apr 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant