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

Not work for content-type #1

Open
Kzinux opened this issue Jan 5, 2015 · 5 comments
Open

Not work for content-type #1

Kzinux opened this issue Jan 5, 2015 · 5 comments

Comments

@Kzinux
Copy link

Kzinux commented Jan 5, 2015

The content-type rule doesn't work,others like useragent,referer,accept-language works fine.

@disptr
Copy link
Owner

disptr commented Jan 5, 2015

Seems to be working. I analyzed the request headers in Firefox's Network Monitor, and Content-Type was set as expected. However, I have done only a minor investigation, so maybe I'm missing something. Care to explain further, share with me the rule in question, etc?

@Kzinux
Copy link
Author

Kzinux commented Jan 6, 2015

Thanks for your reply.

addons.cdn.mozilla.net
Content-Type=text/plain

This is the rule i wrote,then i open a image below,the page's content-type doesn't change.
https://addons.cdn.mozilla.net/user-media/addons/571104/preview.png

@Kzinux
Copy link
Author

Kzinux commented Jan 6, 2015

Sorry, my mistake. I also checked the Firefox's Network Monitor, the request headers's content-type changed, but the Response headers's content-type didn't.
Could you please make the content-type rule works on the Response headers.

@disptr
Copy link
Owner

disptr commented Jan 6, 2015

I will look into adding functionality for rewriting response headers too. I'll put it on my todo list. Not sure when I will have time to get it done, though.

Thanks for the feedback!

@Kzinux
Copy link
Author

Kzinux commented Jan 7, 2015

Thanks a lot! Look forward to it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants