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

Can methods other than GET support Range? #581

Closed
reschke opened this issue Dec 8, 2020 · 4 comments
Closed

Can methods other than GET support Range? #581

reschke opened this issue Dec 8, 2020 · 4 comments

Comments

@reschke
Copy link
Contributor

reschke commented Dec 8, 2020

14.2:

"A server MUST ignore a Range header field received with a request method other than GET."

16.1.2:

"Likewise, if the new method might have some use for partial response semantics (Section 14.2), it ought to document this, too."

@royfielding
Copy link
Member

I can see why someone might want to use it with SEARCH as well, though they would more likely use a page parameter. I can't think of any other use case.

@reschke
Copy link
Contributor Author

reschke commented Dec 9, 2020

FWIW, that's exactly how it was used by MS in Exchange SEARCH: https://docs.microsoft.com/en-us/previous-versions/office/developer/exchange-server-2003/aa123634(v=exchg.65)

We need to decide which of the statements in our spec is correct.

@royfielding
Copy link
Member

Huh, that's news for me. We could have used that example for Range extensions.

@reschke
Copy link
Contributor Author

reschke commented Dec 9, 2020

Change requirement to MUST ignore Range when not defined for that method or the method is unrecognized.

@reschke reschke self-assigned this Dec 10, 2020
royfielding added a commit that referenced this issue Dec 11, 2020
Potentially allow Range handling on methods other than GET (fixes #581)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants