search

orbednetwork / chrome-rest-client

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

Header with 31 chars won't be send to the server #131

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Add a new header "access-control-request-headers" (used for CORS)

What is the expected output? What do you see instead?
Expected: Header will be send to the server - show up in Request headers.
I see: Header doesn't appear. If I one char of the header, it will appear.

On what operating system?
chrome, Win7

Original issue reported on code.google.com by hessmann...@gmail.com on 10 Dec 2012 at 5:32

GoogleCodeExporter commented 9 years ago 
When you open chrome inspector, in console you will see an error like: 'Refused 
to set unsafe header "access-control-request-headers"'. 
It is a limitation of a XmlHttpRequest object not an application.
It will be possible to sen "unsafe" headers when DeclarativeWebRequest API will 
be available in Chrome stable channel. For Chrome beta this is working right 
now very well.

Original comment by jarro...@gmail.com on 15 Dec 2012 at 2:12