Issue 552: Chrome doesn't send user-agent header with CONNECT request http://code.google.com/p/chromium/issues/detail?id=552
Comment #4 by [EMAIL PROTECTED]: The network API does allow the UA string to change dynamically. We don't leverage that in Chrome at all. It would be a reasonable workaround for the beta channel to set the UA string property of the session handle to the UA string value given by the first HTTP request. That said, we may also just wish to wait until the new HTTP stack gets turned on. -- 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 -~----------~----~----~----~------~----~------~--~---
