Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Response Headers support for protocols #37

Closed
Gozala opened this issue Jul 23, 2018 · 1 comment
Closed

Response Headers support for protocols #37

Gozala opened this issue Jul 23, 2018 · 1 comment
Labels
Protocol Protocol API related issues

Comments

@Gozala
Copy link
Contributor

Gozala commented Jul 23, 2018

This is followup from #2 where you can find all the details. Below quote is short summary:

Response Headers - Things don't seem all that great here either. From what I understood there is logic branching based on whether url.scheme is http(s) and if so that is where channel is casted to nsIHttpChannel. It was suggested to add another interface like nsIHttpHeadersChannel that would be able to provide HTTP headers, after which we can update earlier mentioned logic branch to support headers on non http(s) protocols as well. As with Request Headers it seems to require C++ changes which makes it more difficult and requires landing it in Firefox. Although necko team seemed 👍 on accepting such changes.

@Gozala
Copy link
Contributor Author

Gozala commented Aug 7, 2019

@Gozala Gozala closed this as completed Aug 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Protocol Protocol API related issues
Projects
None yet
Development

No branches or pull requests

1 participant