iorewlion.blogg.se - Code on time postback business rule

Maybe I don't see something that is very obvious, so please, help me see it.

What the heck is going on with ASP.net request processing events in global.asax? How is it possible that the first event is EndRequest? I have never seen this behavior before.Īny piece of advice, hint or push in the right direction is welcome.

Problem is obviously related to something Google did to Chrome in the latest version, but why is it so inconsistently occurring? It would be obvious that there is something wrong with my app if it would fail always.

in the failed postback, after the first three events, HTTPContext Items collection and local variables within global.asax are being reset.

for the failed postbacks, the session cookie and most of the other cookies are not available in the first three events (it smells like SameSite issue?) but they are available later in the rest of the events.

for valid postbacks, the session cookie and all other cookies are available.

an invalid postback starts with EndRequest event.

a valid postback starts with BeginRequest event.

I tried all sorts of tricks to try to transfer the postback content form the first three events into the next BeginRequest, but with no success. I really do not understand what is going on and in week-long research, I could not find anything related to my problem.

It seems like the request's content is being reset or disposed of after those first three events, and a new HTTPRequest (or even HTTPContext) is initialized but without content. But from BeginRequest on, there is no request content. Those three events have access to the correct postback content.Īfter those three events, BeginRequest is fired and all events that are supposed to go after it. It is EndRequest, followed by the other two events mentioned above. Normally, for all valid postback requests, the first event triggered is always BeginRequest and the others follow, ending with these three events:īut, in the failed postbacks, BeginRequest is not the first event fired. And what I found got me even more confused.

During the forensics, I implemented all request related event handlers in global.asax on my web site to track what is going on with requests. net Framework 4.8, but it didn't help.īy analyzing error logs I noticed that there is no content in the postback from the payment gateway sent back to my site. I spent some time fiddling with it anyway, I even upgraded my web to. I read about that issue and what to do to make my app support those Google changes, but it seems that the issue is not relevant to my problem because most of the time postbacks work just fine. I suspected that the problem is with cookies and that new SameSite rule Google imposed in this new version of Chrome. All other browsers still work fine, even older versions of Chrome. Then in some instances, not always, only on these new versions of Chrome, some postback requests from the payment gateway started failing. The page accepts postback data and stores it in the database.Ī very simple process that was working flawlessly up until Google released its Chrome v80 browser. After the payment gateway does its magic it posts back the response back to my site on to dedicated web page. I have ASP.net web forms application that integrates with a certain payment gateway.