Page 1 of 1
HTTP 304
Posted: Wed Sep 28, 2022 5:30 pm
by thefunkyjoint
When i try to navigate to Telegram (https://web.telegram.org) using SimpleBrowser, i get the result below and a blank page is shown. Tried to empty cookies and cache, but no lucky. On regular Chrome the page opens normally.
Any ideas ?
HTTP/1.1 304 Not Modified
Server: nginx/1.18.0
Date: Wed, 28 Sep 2022 17:28:29 GMT
Last-Modified: Tue, 15 Jun 2021 08:36:09 GMT
Connection: keep-alive
ETag: "60c86679-3f3d"
Expires: Wed, 28 Sep 2022 18:28:29 GMT
Cache-Control: max-age=3600
X-Frame-Options: deny
Re: HTTP 304
Posted: Wed Sep 28, 2022 6:45 pm
by salvadordf
I just tried to open that address from Windows and Linux and I get the "Log in to Telegram by QR Code" page.
Try changing the user agent string, emulating a cell pone, using a proxy or enabling the Chrome runtime mode.
Re: HTTP 304
Posted: Wed Sep 28, 2022 10:48 pm
by thefunkyjoint
salvadordf wrote: Wed Sep 28, 2022 6:45 pm
I just tried to open that address from Windows and Linux and I get the "
Log in to Telegram by QR Code" page.
Try changing the user agent string, emulating a cell pone, using a proxy or enabling the Chrome runtime mode.
How can i enable the Chrome runtime mode, please ?
Re: HTTP 304
Posted: Thu Sep 29, 2022 7:58 am
by salvadordf
The Chrome runtime mode is in experimental mode and many features are not fully implemented but you can try it in the some demos like MiniBrowser.
Open MiniBrowser and add this line in the
CreateGlobalCEFApp procedure :
Code: Select all
GlobalCEFApp.ChromeRuntime := True;
Then open that web page. If SimpleBrowser can't open that web page but the modified MiniBrowser demo can open it then this issue is probably caused by some form of browser fingerprinting targeting some feature that's not implemented by default by CEF browsers in normal mode.
Re: HTTP 304
Posted: Thu Sep 29, 2022 5:46 pm
by thefunkyjoint
The issue was fixed after i tried a different CEF version.