search

mjrgit / chrome-rest-client

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

Cookie header appears to be stripped at request-time #136

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create a request with a 'Cookie' header.
2. Send the request

What is the expected output? What do you see instead?
In the request/response details below, the request headers are displayed 
immediately after the response status code. However, the 'Cookie' header input 
is not shown in the request headers.

On what operating system?
OS X Mountain Lion (10.8.2)

Please provide any additional information below.
Try changing the name of the header to "C0okie" or "Coookie" (with three 'o' 
characters) and observe that the header is shown as expected. However, when the 
header is named "Cookie", it appears to be stripped from the request.

Original issue reported on code.google.com by tbhuvane...@totsy.com on 26 Dec 2012 at 7:27

GoogleCodeExporter commented 8 years ago 
This feature is available for at least chrome beta channel. Some headers can't 
be set in JavaScript request. It is prohibited in spec. However chrome have new 
api to overwrite this behavior. Soon it should be available for stable channel.

Original comment by jarro...@gmail.com on 26 Dec 2012 at 8:07