points by mahboi 1 day ago | 0 comments
You get 429 if you visit the link directly. Not sure what mechanism is used to tell that, doesn't seem to be the referrer though. This does the refresh to the malware site:
curl 'https://archive.ph/o/jXv3A/https://schenklawfirm.com/wp-content/uploads/2026/10/wan-v-openai-complaint.pdf' \
--compressed \
-H 'User-Agent: [redacted]' \
-H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8' \
-H 'Accept-Language: en-US,en;q=0.9' \
-H 'Accept-Encoding: gzip, deflate, br, zstd' \
-H 'Connection: keep-alive' \
-H 'Cookie: [redacted but you dont need it actually]' \
-H 'Upgrade-Insecure-Requests: 1' \
-H 'Sec-Fetch-Dest: document' \
-H 'Sec-Fetch-Mode: navigate' \
-H 'Sec-Fetch-Site: cross-site' \
-H 'Sec-Fetch-User: ?1' \
-H 'Priority: u=0, i' \
-H 'TE: trailers' \
-H 'Pragma: no-cache' \
-H 'Cache-Control: no-cache' -v[–] opello 1 day ago
[–] mahboi 1 day ago
The page has other links that all go to archive.today. Seems like any link to a PDF causes this to happen. https://archive.ph/Y6BOX near "Download the PDF, which contains the dolls and all of the looks, here." Wonder if it's all links in general that aren't archived.
This looks like some kind of misconfiguration more than intent, or a mix, but it's still bad.
[–] opello 1 day ago
Wow, yeah, same two redirects for that PDF link. Geez. It'd sure be interesting to know the full cause here, otherwise it really destroys a lot of trust in the tool.
Edit: It sure does seem to be a PDF problem, these were both NYT things, but I tried a CCC talk page that had a slides link and sure enough, same behavior.
https://archive.ph/o/n5qxb/https://fahrplan.events.ccc.de/congress/2015/Fahrplan/system/event_attachments/attachments/000/002/825/original/32c3-slides.pdf[–] opello 17 hours ago
Trying these URLs again now and it seems to be redirecting to the right place for all 3 I had tested.
Response headers mention an onion-location and link to stolidityseashellshotter... but also mementoweb... pretty strange. Most generously, maybe some kind of cache poison instead of explicit bad behavior?