-
Notifications
You must be signed in to change notification settings - Fork 29
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
If-Modified-Since is not ignored if request contains If-None-Match #35
Comments
Ah, yes, it looks like this is a new change in the spec, as that requirement was not part of RFC 7232, AFAICT. |
Oh, you're right. That's why I said as far as I can tell. I guess I assumed it would be in the same section in both RFC, doh. |
If you'd like, I could try to create a PR addressing the issue? |
Hi @marco2216 you can, though sorry I didn't post yet, just before you go through too much trouble, I did already start on the |
Oh I see, I'll let you handle it then 👌 |
Hi, sorry to bother you. May I ask if there has been any progress on this matter, or what the follow-up plan is, or if there is a timeline? @dougwilson |
Hi @bigbigDreamer apologies for that! It just got lost in the sea of notifications for me and then fell off more as I got some unrelated security reports I had to triage and working on fixing one of them currently. I think I already pushed up the changeset, so I will get a release made and pushed here. |
Hi @marco2216! Are you still interested in working on this PR? We've completed the migration to GitHub already :) |
Hi @UlisesGascon , I fix this, can u help me review #38 All tests passed! |
Fix: Expect return true immediately if If-None-Match matches the ETag header (#35)
According to the latest HTTP RFC,
fresh
does not ignore If-Modified-Since, it returns false if the If-Modified-Since is before last-modified. I would expect it to return true immediately if If-None-Match matches the ETag header.The text was updated successfully, but these errors were encountered: