01-05-2023, 11:39 PM
(This post was last modified: 01-16-2023, 02:12 AM by Alexandre Machado.)
Regarding the "Invalid Page Context" error.
It is caused by a mismatch when checking the FormID received by the IntraWeb application. I find it hard that it will suffer any influence from the type of application (Http.sys, Indy, ISAPI...) because it is just a content field like any other. If there was something wrong receiving content fields you would see an error right before starting the IW session...
From the top of my head I can't tell you if there was any issue in IW 15.2.49 regarding FormID validation, but we indeed improved it in subsequent releases. The FormID validation will just raise an exception and interrupt the response but this is a treated exception and shouldn't cause any memory increase. Can you tell me if this is a Sync or Async request?
You can turn off the FormID check (in ServerController.SecurityOptions) and see how it behaves. The error should be completely gone then. We would need to investigate what is the request that is causing that and find out why it is happening. But, again, I would expect that Indy and Http.sys behave 100% the same in that regard.
It is caused by a mismatch when checking the FormID received by the IntraWeb application. I find it hard that it will suffer any influence from the type of application (Http.sys, Indy, ISAPI...) because it is just a content field like any other. If there was something wrong receiving content fields you would see an error right before starting the IW session...
From the top of my head I can't tell you if there was any issue in IW 15.2.49 regarding FormID validation, but we indeed improved it in subsequent releases. The FormID validation will just raise an exception and interrupt the response but this is a treated exception and shouldn't cause any memory increase. Can you tell me if this is a Sync or Async request?
You can turn off the FormID check (in ServerController.SecurityOptions) and see how it behaves. The error should be completely gone then. We would need to investigate what is the request that is causing that and find out why it is happening. But, again, I would expect that Indy and Http.sys behave 100% the same in that regard.