DevTools: Add CORS response headers to api requests
Reported by
robing...@gmail.com,
Jul 26 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: Currently unavailable 1. Open dev tools 2. Open network tab 3. Either be able to apply to all XHR (fetch) or right click individual requests (like the block request) and manipulate response headers What is the expected behavior? What went wrong? Currently unavailable Did this work before? No Chrome version: 59.0.3071.115 Channel: n/a OS Version: OS X 10.11.6 Flash Version: It would be really handy if we could add the response header: Allow-Control-Allow-Origin: * onto API calls and/or manipulate other response headers when using developer tools in chrome and from the DTP. Here is an example chrome extension that does some of this: https://chrome.google.com/webstore/detail/allow-control-allow-origi/nlfbmbojpeacfghkpbjhddihlkkiljbi?hl=en
,
Jul 31 2017
,
Jul 31 2017
,
Aug 2 2017
I previously focused only on adding CORS however it would actually be useful to be able to access the headers of the response too with: access-control-expose-headers So maybe just being able to add/edit any headers would be useful. on a API / Domain basis?
,
Dec 14 2017
Closing as WontFix due to lack priority / resources. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ranjitkan@chromium.org
, Jul 27 2017