vercel/fetch returns 404 for calls that were returning 200 prior about fetch HOT 5 CLOSED

I'm seeing the same behavior with node-fetch, where the result is intermittently 404 (on any tweet syndication url), although I'm not sure why yet. I'll keep digging, but I don't think this bug is specific to @vercel/fetch.

from fetch.

The same behavior occurs using the underlying node:https module directly, so this is definitely not an issue with @vercel/fetch afaict.

The first GET is always successful, and subsequent GET requests 404. If you override the agent to disable TLS session caching, then everything works fine.

from fetch.

hey @transitive-bullshit, you managed to fix the issue over here. Did you figure out if the issue is related to TLS session caching? If so, I can close this up.

from fetch.

Yep; I don't think this has anything to do with @vercel/fetch.

from fetch.

Thank you for the report. We are archiving this project; you can read more details here: #83

from fetch.