When using Developer Tools Set-Cookie fails

SDK/Debugger version:
Eclipse version:
Google Chrome/V8 Embedder + version: 41.0.2272.76 m
[For WebKit (WIP) protocol] Backend version:
OS + version: Windows 7

What steps will reproduce the problem?
1. Activate the developer tools
2. Do a request to a server doing custom NTLM authentication using cookies to 
identify requests
3. The server answers with a 401 tells that he would like to do NTLM and also 
sends a Set-Cookie

What is the expected result?
The client should send another request replying to the NTLM challenge 
containing the newly set cookie.

What happens instead?
The client sends the request containing the reply to the NTLM challenge but an 
old cookie. It does however send the right cookie if Developer Tools are not 
active.

Please provide any additional information below. If possible, attach a
(reduced) test-case.

Here my original text without the suggested format which might make my 
situation clearer:

I'm using Chrome version 41.0.2272.76 m and want to use the Developer Tools on 
my website. This website has a custom NTLM authentication using cookies to 
identify the requests. If running in normal mode this works fine but once I 
activate the developer tools the Set-Cookie from the server seems to be 
ignored. This means it will send an old cookie and not the one the server just 
set in the request before.

Is this some setting in the developer tools I can change? 

The custom NTLM is hosted by me in my Intranet so I'm sorry to say that I can't 
supply you with an address to check this but maybe this is unrelated to NTLM 
and can just be reproduced by using Set-Cookie with Developer Tools open and 
see if it takes the latest cookie in the next request

Thanks for any help,
Stefan

Original issue reported on code.google.com by StefanAB...@gmail.com on 6 Mar 2015 at 7:33

kashiwazakinenji / chromedevtools

When using Developer Tools Set-Cookie fails #106