IE https double POST submission

[taufikj]

Currently, we have an IIS website application (https) with integrated
windows authentication only.

It seems there is a problem with IE 6.0 that have double submission
"POST".

When a user submit data over, the application executes but because of
the sheer size of data and actions, the appliction sometimes would take
more than 2 minutes. We noticed that the data is resubmitted again
"POST" after some time; when tracing the network but there was no
indication or information from the browser that it will do another
POST. As a result, we have 2 running processes with the same data on
the web server.

The issue is that the user stated that previously it was working (no
such problem) but now it seem to be more of double POSTing. We suspect
it is due to the security patches that affect the way IE post the data
over. However, searching on the MS KB as well as this newgroup indicate
such problems but it was a few years back (2004) and I am not sure if
it is still applicable now.

Have anyone encoutered such a problem that started recently (up to few
months ago)? Is there any solution to this? I have tried this over
Firefox browser and has face no such problem.

 

[Rob Parsons]

Hi taufikj,

I am only guessing, but there may be a web server setting for time-outs for
request processing which is sending back a re-post response.
Its a bit discerting that it is taking so long to do your post processing. I
would be looking at reducing the processing time. You could also try placing
response.write statements at various points in your scripts to give the user
an indication of processing

 

[taufikj]

Thanks for the reply. Appreciate it.

The processing of the application would take some time as it is
expected for such load and its actions.

But if it was web server settings; why did it had not occur before and
why is it Firefox browser is looking fine?

I have tested previously that in disabling the https in the server; it
works just fine in IE. I will retry this route again. The only pain is
really of HTTPS problem which seems so persistence in IE case thru
security updates.