|
<< Click to Display Table of Contents >> Navigation: Telegram > 2024 > 01 > 07 > Telegram_2024-01-07T21 |
2024-01-07T21:20:56
I rebuilt and deployed the MultiPageApp IW demo with httpsys in Delphi and couldn't get the error with GotoURL. I changed the OnClick for IWButton1 to WebApplication.TerminateAndRedirect and now get an error from the demo in both edge and firefox, The firefox error seems to be different than edge, it shows 'The page you are trying to view cannot be shown because the authenticity of the received data could not be verified'. The MultiPageApp demo is deployed at type: link https://support.mjs.us .
2024-01-07T21:23:14
Yes, I see the problem
2024-01-07T21:23:43
I'm getting the same issue with FF on my local environment
2024-01-07T21:24:21
Im on 5.3.x didnt see the issue. Ill check ffox just to see
2024-01-07T21:31:39
I'm getting the same thing with IW 15.3.10
2024-01-07T21:32:56
and also with 15.2.69
2024-01-07T21:46:45
On edge if you click on the little icon left of the url it gives this message - 'This site does not have a certificate. Because this connection is not secure, information (such as passwords or credit cards) will not be securely sent to this site and may be intercepted or seen by others.' It's as though it's losing the SSL connection in the middle of the redirect.
2024-01-07T21:50:12
What I can say for now is that somehow the first request after the redirection fails at the protocol level (way before IW server is involved with it) and the browser retries it. But once the session has been terminated in the previous response, the retry receives a \session timeout error\ with an http 500 status.
Once I'm building with IW sources, I changed slightly the TerminateAndRedirect() method to not terminate the session immediately, but after 15 seconds. Then it all works transparently, because the browser retry will work
2024-01-07T21:55:38
Yes, this is in accordance with what I mentioned above.... seems that at the protocol level something is happening. I'll need to debug the http.sys server and check if this is happening inside IW code or even before IW receive any browser data