When a URL is submitted via the UI, ArchiveBox serves up a 302 redirecting the browser onto a page.
"POST /add/ HTTP/1.1" 200 3593
"GET /add/ HTTP/1.1" 200 7075
We don't need to follow that.
In fact, more than that, we don't want to follow it because it sometimes hangs rather than responding.
Activity
10-Aug-24 16:13
assigned to @btasker
10-Aug-24 16:13
mentioned in issue #6
10-Aug-24 16:16
Closing as
Invalid
- I was having a brain-fart.That
GET
isn't us following a redirect, it's the next request scraping the CSRF token.Reckon it might be time to stop and do something else for a bit :)