Issue 552: Chrome doesn't send user-agent header with CONNECT request http://code.google.com/p/chromium/issues/detail?id=552
Comment #6 by [EMAIL PROTECTED]: I implemented a fix by passing a user agent string to WinHttpOpen. The changelist is being reviewed at http://codereview.chromium.org/8841. I verified that setting a user agent string on the session handle (either in WinHttpOpen or with WinHttpSetOption) is the only way to specify the User-Agent header for HTTP CONNECT requests. Passing a User-Agent header to WinHttpAddRequestHeaders or WinHttpSendRequest doesn't affect the HTTP CONNECT requests. Issue attribute updates: Status: Started -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to chromium-bugs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
