Expose response headers
See original GitHub issueIn my project, users deploy simply by pushing their code, the server builds it and deploys it and sends back the deployment data back to the client. Currently I’m parsing the message
event which is not super robust. A better approach would be to return data in an HTTP header but those are not exposed for fetch
/pull
/push
.
Do you think it would make sense to expose the HTTP in the results of network operations?
Once again, thanks @wmhilton!
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Why is Access-Control-Expose-Headers needed?
If you want clients to be able to access other headers, you have to use the Access-Control-Expose-Headers header. The value of this header...
Read more >Access-Control-Expose-Headers: Syntax, Directive, Examples
Access-Control-Expose-Headers is an HTTP response header that determines which headers are to be exposed to the client scripts on a web ...
Read more >HTTP headers | Access-Control-Expose-Headers
The HTTP Access-Control-Expose-Headers header is a response header that is used to expose the headers that have been mentioned in it.
Read more >Access-Control-Expose-Headers - DigitalOcean Documentation
Access-Control-Expose-Headers is a header request that allows a server to show which response headers are available to scripts running in the browser.
Read more >Access-Control-Expose-Headers - HTTP - W3cubDocs
The Access-Control-Expose-Headers response header allows a server to indicate which response headers should be made available to scripts running in the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It seems like the git client handles it as a protocol error [1]. Like you said, not friendly to vendor-specific extensions.
[1] https://github.com/git/git/blob/7e8bfb0412581daf8f3c89909f1d37844e8610dd/sideband.c#L202-L205
Yeah I use that for my cli client to send auth and metadata that shouldn’t be version controlled. I’m about to implement this on the web version so I’ll be indeed needing it pretty soon! Thanks for preemptively asking
On Mon, Oct 15, 2018, 9:33 AM William Hilton notifications@github.com wrote: