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

Supporting 425 Too Early #2291

Open
pvichivanives opened this issue May 17, 2024 · 3 comments
Open

Supporting 425 Too Early #2291

pvichivanives opened this issue May 17, 2024 · 3 comments

Comments

@pvichivanives
Copy link

I was wondering if there was a reason reqwest don't support HTTP response status code 425 too early:

RFC Here: https://datatracker.ietf.org/doc/html/rfc8470

If this seems reasonable to add I'm happy to go through the code and raise a PR for this.

@seanmonstar
Copy link
Owner

I read through the RFC. Before writing code, what exactly would you hope it would do?

@mohe2015
Copy link

I would assume the relevant part is

Clients that use early data MUST retry requests upon receipt of a 425
(Too Early) status code; see Section 5.2.

So the question is whether reqwest supports early data

@pvichivanives
Copy link
Author

Honestly, I was thinking of adding a reqwest::StatusCode::TOO_EARLY just to add an easy way for users to deal with it in case the server mistakenly returns it (I'm assuming that reqwest doesn't support early data or else this status code would already exist). Looking at it again today though, I just noticed that this was a re-export of HTTP StatusCode so maybe I'm making this request in the wrong place?

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

No branches or pull requests

3 participants