3 ms·
A helpful way to debug this is the "copy as Curl" feature in most browsers. That should give you the most true representation of what request is being sent to H
by ghiculescu 5y ago
A helpful way to debug this is the "copy as Curl" feature in most browsers. That should give you the most true representation of what request is being sent to HN. Do it in private mode and non-private mode and then compare the differences.
The screenshot is probably out of date but here's how to use it https://everything.curl.dev/usingcurl/copyas#from-firefox https://everything.curl.dev/usingcurl/copyas#from-firefox
If you do this in chrome you'll get a long curl command that ends like this:
--data-raw 'goto=item%3Fid%3D30166448&acct=ghiculescu&pw=(YOUR PW)' \
--compressed
I found it most helpful to change that to
--data-raw 'goto=item%3Fid%3D30166448&acct=ghiculescu&pw=(YOUR PW)' -v
So you can also see the response headers etc.