ncarlos / clickonceforchrome

Automatically exported from code.google.com/p/clickonceforchrome
0 stars 0 forks source link

How about setting the X-ClickOnceSupport header? #5

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Like Chrome, Firefox now prevents add-ins from changing the user agent string.  
The solution implemented by the .NET plug-in for Firefox is to set the 
X-ClickOnceSupport header.  See 
https://connectppe.microsoft.com/VisualStudio/feedback/details/667720/microsoft-
net-framework-assistant-1-2-2-for-firefox-does-not-report-net-version-in-user-ag
ent 

Might that also be possible in a future version of ClickOnce for Chrome?

Original issue reported on code.google.com by johnmr...@gmail.com on 4 Aug 2011 at 10:32

GoogleCodeExporter commented 8 years ago
Unfortunately I haven't been able to find any way (horrible hacks aside) to 
make this work with Chrome.  Firefox lets you register a request 'observer' 
that can use script to set the header before it goes out but there isn't an 
equivalent in Chrome (afaik).

Original comment by e...@digitalsorcery.net on 4 Aug 2011 at 11:46

GoogleCodeExporter commented 8 years ago
Looks like this might be possible in new versions of chrome.  Still marked as 
experimental but it looks promising.

http://code.google.com/chrome/extensions/experimental.webRequest.html#event-onBe
foreSendHeaders

http://code.google.com/chrome/extensions/experimental.webRequest.html

Original comment by erichard...@gmail.com on 6 Feb 2012 at 4:49

GoogleCodeExporter commented 8 years ago
FYI:
Message from 
http://developer.chrome.com/extensions/experimental.webRequest.html:

The WebRequest API is no longer experimental; it's supported! You can read all 
about it at its new home:
chrome.webRequest

http://developer.chrome.com/extensions/webRequest.html

Original comment by kha.th...@gmail.com on 20 Aug 2012 at 11:39

GoogleCodeExporter commented 8 years ago
This is now being planned.

New issue located at: 
https://code.google.com/p/clickonceforchrome/issues/detail?id=19

Original comment by bionicma...@gmail.com on 8 Oct 2014 at 11:07