Atozed Forums

Full Version: Server 2022
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have to move from Windows Server 2016 to 2022 shortly.  I've found an issue which looks to be related to httpsys and SSL.

This code works correctly on httpsys/SSL/Server2016 or non SSL from an OnClick event:

Code:
WebApplication->TerminateAndRedirect(url); and
WebApplication->Response->Cookies->AddCookie()

On httpsys/SSL/Server2022 (Non SSL works) I get blank page with this:

ERR_HTTP2_PROTOCOL_ERROR

Also, the behavior of this is different from OnClick and OnAsyncClick:

Code:
WebApplication->Terminate(custom message);

OnClick goes back to main form with new session, OnAsyncClick works correctly by showing the custom message.  This seems not related to httpsys, etc.
This has been fixed and will be available in the next update, IW 15.5.5

As I said on our telegram channel, the problem happens because of duplicate Set-cookie headers in one of the responses.
It works on every other Windows version and also on Windows 2022 if using HTTP (not HTTPS), which is odd. Seems that MS slightly changed one of their APIs.

Anyway, the problem is solved in our code base
This has been fixed in IW 15.5.5

https://www.atozed.com/2024/01/intraweb-15-5-5/

Cheers,
(01-10-2024, 12:24 AM)Alexandre Machado Wrote: [ -> ]This has been fixed in IW 15.5.5

https://www.atozed.com/2024/01/intraweb-15-5-5/

Cheers,

Hi Alexandre! We encountered the ERR_HTTP2_PROTOCOL_ERROR when testing https to one of our web applications on Windows Server 2022, directly when trying to access our login page (http worked, and we have never seen it on other Windows versions). I found this post and it sounds like it could be the same thing to me. Our build environment is currently set up for IW 15.2.49, including 3rd party libraries for TMS and CGDevTools. Is the above fix very isolated, so that it would be possible to "cherry pick" it into the relevant unit(s) for 15.2.49? If so, we could verify if the fix takes care of our case as well, and know if it would be worthwhile starting a migration project to the latest IW version (including the 3rd party components).

Best regards

Magnus Oskarsson
Hi Magnus, yes I believe so.

I'll need to inspect the affected code before getting back to you with any details about this fix.
Hi Alexandre and thanks for getting back! Sorry for a little late response from me, have been on vacation.

We are still very much interested in getting a patch that would work for IW 15.2.49, as we need to resolve this in rather short term for a large customer of ours. While we will also look at migration to the latest IW version, that project has grown much larger due to the announcement from CGDevTools that they will discontinue their component packages for IntraWeb. (Two of our web applications rely heavily on CGDevTools mobile components, and we also use a few things from their "standard" jQuery suite).

Best regards

Magnus Oskarsson