search

orbednetwork / chrome-rest-client

Automatically exported from code.google.com/p/chrome-rest-client
0 stars 0 forks source link

Setting Accept-Charset header for request not working #160

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. I am trying to access a REST web service hosted on my local machine. I am 
setting the Accept-Charset: utf-16 and trying to send the request. 
When I click on send, the request summary shows utf-8 only as charset. 

What is the expected output? What do you see instead?
please see the attachment. 

On what operating system, browser and browser version?
Chrome on Windows 7 64 bit. 

Please provide any additional information below.

Original issue reported on code.google.com by nair.nis...@gmail.com on 15 Feb 2013 at 9:32

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi, Thanks for issue report.

Unfortunately there is good reason for this behavior. Guessing you are using 
Chrome Stable Channel (v. 24 or 25). 
Within current stable version it is impossible to set some headers marked by 
spec as "unsafe". When you check console output it should print something like: 
"Refused to set unsafe header "Accept-Charset"". It is a javascript error and 
now I really can't do anything with it. 
However there is new API which make it possible. It is in Chrome beta now and 
lately Chrome Team announced that it is possible that the declarativeWebRequest 
API (I'm talking about this API) will be moved to stable channel on next 
update. 
I'm hoping it will happen because we all waiting to enable this feature.

For now I can't help you. Only way is to use chrome beta channel which is 
already supporting this feature.

Original comment by jarro...@gmail.com on 22 Feb 2013 at 1:24