On Tuesday, 4 August 2020 09:34:49 PDT Mårten Nordheim wrote:
> Sure! ws://[::1] also worked for me.
Takk, Mårten.
Alexander: can you try that? And please make your websocket server bind to
local host, so it cannot be accessed from the Internet or LAN.
--
Thiago Macieira - thiago.macieira (AT)
Sure! ws://[::1] also worked for me.
Mårten
From: Interest on behalf of Thiago Macieira
Sent: Tuesday, August 4, 2020 18:21
To: interest@qt-project.org
Subject: Re: [Interest] wss:// on localhost
On Tuesday, 4 August 2020 07:44:06 PDT Mårten Nordheim w
On Tuesday, 4 August 2020 07:44:06 PDT Mårten Nordheim wrote:
> Ah sorry. What I meant is that I had a secure website
> (https://myothercomputer/app.html) which initiated a websocket connection
> to ws://127.0.0.1, and it works fine. You have to use "127.0.0.1" in this
> case and not "localhost" du
Thank you Henry. I’ll try updating the driver on that machine.
I recently tried on a newer system, and that one also had problems with
transparent windows.
Here’s the specifications for that one:
> 3D Device
> Vendor : NVIDIA Corporation
> Video Processor 1 : Intel(R) UHD Graphics Family
> Vide
Hi, I think GTX 950M is too old (the laptop is from 2015) for Direct3D
12, see for example:
https://www.nvidia.com/en-us/geforce/forums/discover/234361/gtx-950m-dirextx-12/
Also, the driver for the Intel HD 4600 is a bit old, try updating it
from 20.19.15.4549 to 20.19.15.4853, it might help f
> 4) It's also a shame how the Internet has become - I still have a mindset of
> the year 2000 where the web was not really a significant resource of criminal
> intent. I understand this can lead to misunderstanding ;-)
If you open up port 80 or 443 on a AWS-hosted instance with a public IP, wi
Hello,
If you are targeting Windoows10, you could try to use Direct3D 12 renderer with
Qt 5.15.x ==> https://doc.qt.io/qt-5/qtquick-visualcanvas-adaptations-d3d12.html
Regards
Fabrice
Von: Interest Im Auftrag von Furkan Uzumcu
Gesendet: Dienstag, 4. August 2020 16:33
An: inter...@lists.qt-pro
Ah sorry. What I meant is that I had a secure website
(https://myothercomputer/app.html) which initiated a websocket connection to
ws://127.0.0.1, and it works fine.
You have to use "127.0.0.1" in this case and not "localhost" due to the fact
that you can remove or change what "localhost" should
Hello everyone.
I’ve been having this issue on NVIDIA cards on Windows in all versions from Qt
v5.12.2 to v5.15.0. I created a ticket here:
https://bugreports.qt.io/browse/QTBUG-85524
But I wanted to reach out to see If anybody else encountered this. I’m not that
well versed in this issue. I’m
Hi Marten,
>> Looking at https://letsencrypt.org/docs/certificates-for-localhost/ they
>> mention that "modern" browsers let you make insecure connections to
>>127.0.0.1.
>> Tested locally with a secure website connecting to ws://127.0.0.1 and it
>> works fine. Which browsers do or don't suppor
Looking at https://letsencrypt.org/docs/certificates-for-localhost/ they
mention that "modern" browsers let you make insecure connections to 127.0.0.1.
Tested locally with a secure website connecting to ws://127.0.0.1 and it works
fine. Which browsers do or don't support it I'm not sure though, b
>> A conventional html page (classical web browser) launches a websocket via
>> wss://localhost:1234 and connects to a Qt
>application which hosts a QtWebsocket Server which binds to localhost:1234.
>This way I achieve communication between browser
>>and app. Would love to stay with ws:// but mod
12 matches
Mail list logo
