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

Conditional HTTP requests broken? #4345

Open
ehamberg opened this issue Aug 3, 2024 · 3 comments
Open

Conditional HTTP requests broken? #4345

ehamberg opened this issue Aug 3, 2024 · 3 comments

Comments

@ehamberg
Copy link

ehamberg commented Aug 3, 2024

Not any specifics, unfortunately, but from http://rachelbythebay.com/w/2024/08/02/fs/ it sounds like NetNewsWire (or its HTTP library, I guess) is not doing conditional HTTP requests correctly:

NetNewsWire. Bigtime brokenness in their IMS/INM caching. No idea why, but it makes it generate unconditionals constantly.

NetNewsWire. Just like the earlier one, broken caching and crazy timing.

NetNewsWire. Same bad caching and timing stuff.

NetNewsWire. Broken, as above.

NetNewsWire. Bro-ken.

NetNewsWire. Broken record.

@trekzavier
Copy link

Sounds about right, open rsss talks about issue too in https://openrss.org/issue/54

@brentsimmons
Copy link
Collaborator

We already have a bug about OpenRSS and rate limiting: #4224

And I’m not too concerned about the timing issues in Rachel’s report — you can do a manual refresh any time you want in NetNewsWire, and that will result in a new request. So any crazy timing is just that.

But the conditional GET bugs are concerning. Here’s the actual report: https://rachelbythebay.com/api/fsr/4467c09c31370b8375c6b2a320aa77cd5d999cd4

(I had the test feed running on my personal laptop, and it reflects my use. You can even see when I went on a long vacation and left the laptop at home.)

I’ve identified one issue — I don’t know if it’s the only one or not. Here’s the scoop:

If the server returns a raw feed that is unchanged from the previous request, we ignore any updated Last-Modified or Etag headers. We make the assumption that those headers would not have changed if the raw feed hasn’t changed. This is surely true almost all the time in the real world!

There may be other issues too, of course, and it’s possible my theory isn’t the cause of the issues here. But it’s still a thing to fix.

I’ve asked Rachel to add a column for http response code — I have a suspicion that this might tell me more. Fingers crossed that the data is available and added to the report.

@brentsimmons
Copy link
Collaborator

Follow-up: I asked Rachel about the http response codes for the test feed — it’s always 200.

Blogged about this: https://inessential.com/2024/08/03/netnewswire_and_conditional_get_issues.html

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