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

No longer producing Location HTTP Response header #472

Closed
jimsteel opened this Issue Oct 18, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@jimsteel

jimsteel commented Oct 18, 2016

I've noticed that since switching to 2.1-SNAPSHOT, PUT/POST requests are no longer producing the Location header (the Content-Location header is still there, though, with the same value). Is this intended?

@jamesagnew

This comment has been minimized.

Show comment
Hide comment
@jamesagnew

jamesagnew Oct 26, 2016

Owner

Oops! Early in the DSTU3 development process we decided to get rid of one of the two headers since they were redundant.

Possibly I'm remembering this part wrong but I think we picked for Content-Location to be the one that survived. Either way, it's definitely Location now in the spec so HAPI's doing the wrong thing.

I'll update.

Owner

jamesagnew commented Oct 26, 2016

Oops! Early in the DSTU3 development process we decided to get rid of one of the two headers since they were redundant.

Possibly I'm remembering this part wrong but I think we picked for Content-Location to be the one that survived. Either way, it's definitely Location now in the spec so HAPI's doing the wrong thing.

I'll update.

jamesagnew added a commit that referenced this issue Oct 26, 2016

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