I am trying to force Google Chrome to use QUIC as the underlying protocol instead of TCP.
I used this command to force QUIC through the command line, but it doesn't work:
chrome --disable-setuid-sandbox --enable-quic --origin-to-force-quic-on=IP:443 http://IP:443/
Wireshark shows me that Google Chrome is still using TCP for that destination.
BTW i am using google chrome Version 97.0.4692.71
Can anyone help me in that matter.
just trying to find a solution for chrome to use http3 without forcing it to, does not work for my local nginx-quic setup, firefox works out of the box... Just found your question. If i remember correctly you can only pass a single domain with that flag to chrome. This works for me:
--origin-to-force-quic-on=mylocaldomain.local:443
Related
I have a website that supports HTTP2. If I use Firefox or Chrome in anonymous mode then all the calls are made with HTTP2 (shown as h2 in Chrome developer tools Network tab).
When I use ordinary Chrome though it does exactly the same call but uses HTTP1.1 for some reason. I have tried to turn of all extensions but it is still HTTP1.1.
Sometimes if I restart Chrome is starts using HTTP2 again but then falls back to HTTP 1.1 after a while or after one of the restarts. I cannot figure out what can be the problem and it looks very mysterious.
I did not change any settings explicitly in Chrome if they even exist. What can be the problem here?
P.S. I did "clear browser cache" and "clear browser cookies" and suddenly I got only http2, don't know how this ca affect protocol. This was a temporary improvement though and I got http1.1 after a while again
P.P.S. I have even got a case when loading a website that one request was http1.1 but the other one was http2 to exactly same server.
Is there any way to access the Microphone and Camera using chrome when the website is http?
I tried enabling "Insecure origins treated as secure" flag, however when the browser is closed and opened again, the domain used in this flag disappears and I have to retype and re-enable it again.
I also tried starting chrome with "--unsafely-treat-insecure-origin-as-secure=http://example.com" argument, however when this was used a message appears on Chrome saying
You are using an unsupported command line
flag:--unsafely-treat-insecure-origin-as-secure=http://example.com.
Stability and Security will suffer
I don't want the message to appear, so I couldn't use this technique as well.
Is there any other way to access the Microphone and Camera without getting any warnings? (I am accessing the device using WebRTC).
This worked for me. Although it's for Testing purpose only.
To ignore Chrome’s secure origin policy, follow these steps.
Navigate to chrome://flags/#unsafely-treat-insecure-origin-as-secure in Chrome.
Find and enable the Insecure origins treated as secure section (see below).
Add any addresses you want to ignore the secure origin policy for. Remember to include the port number too (if required).
Save and restart Chrome.
Remember this is for dev purposes only. The live working app will need to be hosted on https for users to be able to use their microphone or camera.
"unsafely-treat-insecure-origin-as-secure" flag is not working on Chrome
You are not allowed to run webrtc on http after Chrome 47+ version, but you can do some hack for this with some changes in ngnix.cong file, as
//Make necessary changes
server {
listen 8080;
server_name localhost;
location / {
proxy_pass http://your.dev.box.ip:8080;
}
}
Reference : https://webrtchacks.com/chrome-secure-origin-https/
Update: this flag trick from Nafees Ahmad works for Chrome 89, also Chrome Android (I use huawei Mate 20 pro). It helps the website on Chrom access camera or NFC function.
I am trying to implement and use the Chrome Speech API on my website but I'm not able to do it. The response I receive is that the "Permission to use microphone is blocked" but it really isn't. Microphone settings in Chrome are clearly showing that I don't have sites blocked and that the system should it least ask.
It is not a problem with the website because I have performed tests on other computers and it is working fine. I would like to figure out the settings/preferences that need to be readjusted in order to make this work.
In addition to this, in C:\Users\MY-USER\AppData\Local\Google\Chrome\User Data\Default\Preferences I was able to see entries for my site and I removed them but nothing changed. I tried also (not in order:
1- Reset Chrome.
2- Uninstalling/reinstalling Chrome. Manually removing files and registry entries.
3- Run Chrome in incognito mode.
4- Run ChromeCleanup Tool
5- Not working on Chrome Canary.
6- Every computer was tested on the same internet connection.
I am not sure what else I can do about this.
Thanks!
I am currently experiencing an error everytime I use my Microsoft Edge. Whenever I try to go to a site, I always end up with this error. The weird thing is, this issue only happens on certain websites (such as Facebook and Yahoo currently) and sometimes with Google. It likes to disconnect me often and I really don't want to have to deal with this issue anymore.
My internet works fine as my laptop (which I'm currently on) and phone can connect to it without issue. I don't know why it doesn't work on my desktop especially since its internet is Ethernet.
I tested this on other browsers to see if it was only on Edge but it turns out that chrome and firefox experience the same issue with different sites as well. For all three, I haven't been able to go on Facebook and Yahoo, and sometimes Google.
I know the problem is from my end because clearly, the sites are up. Is there any way to solve this or has anyone else found a solution to this?
I'm running Windows 10.
I've tried the following:
ipconfig / flush
ipconfig / reset
ipconfig / release
ipconfig / renew
clearing caches and browsing history
a full scan for malware using malwarebytes and windows defender, already removed/quarantined all threats, did this multiple times to ensure there were none left
reinstallation of chrome and firefox and a reset of edge
ipv4 - changing preferred and alternate dns address to 8.8.8.8 and 8.8.8.4 respectively
checked to see if a proxy was up, no proxy
If I were to do a factory reset, would this solve the issue?
To narrow it down a bit, can you confirm that you only get this when navigating to the sites listed and they're using SSL / HTTPS? Some will auto re-direct to HTTPS if you go to their non-SSL equivalent, but it's worth trying this on sites like Google which do support both.
If this does help narrow down the behaviour, then I've seen this behaviour once before, but this was behind a corporate proxy which didn't support SSL SPDY.
You can try disabling SPDY support, but there is likely to be an underlying issue (perhaps anti-virus acting as a proxy?).
To test disabling SPDY:
Internet Explorer 11
In the browser, select Tools > Internet Options > Advanced > HTTP
Settings and clear the Use SPDY/3 option.
Firefox
In the browser, enter about:config in the address bar and press
Enter. Confirm the security warning. Type
network.http.spdy.enabled in the Search field. For all the entries, set the Value to false.
Chrome
Use a switch to disable SPDY for Chrome. Edit the shortcut for Chrome
and add the following switch at the end of the Target path:
--use-spdy=off
For example, if Chrome's default shortcut link is pointing to
"C:\Program Files\Google\Chrome\Application\chrome.exe", change it to
"C:\Program Files\Google\Chrome\Application\chrome.exe" –use-spdy=off.
Source:-
http://bluecoat.force.com/knowledgebase/articles/Solution/HowtodisableSPDYprotocolsupportinbrowsers
I had a caller who was getting the "can't load page" error in Chrome only when logging into the AMEX site. Every other browser worked. The fix was to disable some weird experimental Chrome setting that is on by default. Go to chrome://flags, search for "experimental quic protocol" and "Disable" it.
Source
Click on start/control pane/IE options/Privacy Tab/Sites
Look at list of sites to see if any Google sites are blocked.
We have a web application that runs within a VPN. It has a self signed cert on it and is accessed through the server's IP address.
Part of the functionality of this app are some legacy Java apps (that no longer run in Chrome). Our initial work around for our Chrome users was to run Shell In A Box within an iframe of the web app to run those. All was good until the latest version of Chrome, v45.
What we’re seeing is that appears to be blocking the iframed content (maybe because of the self-signed cert?). If we grab the ShellinABox URL and drop it in a new tab, it works as it used to in the iframe. If we go back to the iframe, it now works. If we close Chrome and open it back up, it still works.
I should also note that we tried the canary builds as well. It's up to v47.x and we still see the same behavior there. We were reading through some of the Chrome group/bug lists and saw some reports that were similar but the "fixes" supposedly going through canary still didn't resolve it.
So, it appears that an exception is being logged somewhere. Does anyone have an explanation for this behavior and is there a way to set this exception without jumping through those hoops?
It turned out it was due to a permissions issue with ShellInABox that didn't reveal itself until v45 of Chrome, for some odd reason.