Hacker News Reader

I'm not sure I understand the "Override network response headers" feature.

Haven't the responses already been handled? Assuming no time travel, it's not clear what actually happens after you edit a response header.

View on HN

Javascript and the browser use the response headers. The example they gave is overriding CORS. Let say you're running code locally and using remote APIs. Now you can override CORS to allow your local code to still call the APIs.

That's incredibly useful! Dev and staging environment setup involves proxies, SSL, CORS, etc., and can be a total nightmare.

If they integrate request header modification, we can get rid of cookie tools and plugins such as ModHeaders.

This is a really great dev experience improvement.

It's an override, so I imagine future requests will follow the header changes you institute. Now all we need is response editing to really integrate burp/mitmproxy-esque response hacking.

We already have response editing. You can save a file in devtools and set up workspace folders to override responses at any url.

This is an improvement to that feature which allows you to modify the response headers in addition to the response body.

That’s only for GET requests, isn’t it?

Reply on news.ycombinator.com