IE NOT PASSING VARIABLES CORRECTLY ***PLEASE HELP***

[Adam]

Hi there,

I am a customer support agent for Lovedreamer.com. We are having some
problems lately with our site functioning in IE browsers and hoped
someone
here may be able to shed some light on the issue. If anyone can help
us
resolve this issue we will be happy to offer them a $50 gift
certificate
for our online store, we have lots of fun stuff :- )

We are having problems recently with hidden variables not being passed
on a
form post via the ssl enabled server.

Webserver is apache v1.327 with openssl v0.96g. Works perfectly with
all
netscape browsers, and just started having problems with IE over the
past
week or so.

Our server is running redhat linux v8.

Has anyone heard of this or seen a similar problem with other sites ?
We
are hoping we are not the only ones in this position. Any help is
extremely
appreciated here.

btw: the result of this error is that we cannot process CC payments
properly
for users with IE, Netscape works well though, who would have figured
that ?

Sincerely,
Adam

 

[R. Goodwin]

We, at www.traderonline.com & www.traderpub.com, are
having the same exact issue. We have not isolated the
problem yet while we've tried several options.

We have isolated the problem to IE 5.5 & 6.0 that have the
patch: Q832894 (as it appears in the help-about in the
browser). That's the much-hyped Cumulative Security Path
from last Friday (02/06/04).

Things we've investigated:

*Using enctype="multipart/form-data" in the <form> tag.

*Dynamically naming the form fields (the thought being
that the patch is keying off of some sort of credit
card/password/username field for it's Passport software).

*Verified our secure certificates match the domain.

 

[Guest]

Hello

I am going take a wild throw at this. Open Internet Options and go to the Advanced tab. Look and see if "Do not save encrypted pages to disk" is enabled. Maybe playing around with this. Another idea is to look at the active x section of the security tab of internet options. Lower the default level to low and see if that changes things. Perhaps changing one of the Active X settings and enabling more options will allow this to process correctly? Again, I'm just throwing ideas out based on the client machine.

 

[Don Varnau]

This is almost certainly being caused by the recent Update for IE
http://www.microsoft.com/technet/treeview/?url=/technet/security/bulletin/MS04-004.asp

There are some workarounds (from both sides- user and website) in
http://support.microsoft.com/?kbid=834489

Inexperienced users should probably uninstall the patch (832894) as a
temporary fix.

Experienced users could make the registry edits in that article.

This may be relevant, but it applies to the browser- not the website.
831167 - Wininet retries POST requests with a blank header:
http://support.microsoft.com/?kbid=831167

Hope this helps,
Don

 

[Ainur93]

We are having the same issue with IE 5.5 SP2. 831167 only fixes IE 6.
Our users can't use Https sites. Anyone know of a fix for IE 5.5
SP2?

 

[Guest]

I have loaded the 831167 patch, but that did not fix my problem in IE6. I uninstalled the patch, but it still will not let my user recieve the authorization reply screen to tell her the credit card went through. I do not want to format this pc. Does anyone know a workaround or is MS planning on putting out a fix for this problem?

 

[Robert Aldwinckle]

still will not let my user recieve the authorization reply screen

Is that in a popup window? Perhaps she has a popup stopper?

In any case it doesn't sound much like the OP problem (or the first Me too!)

Have you asked them to try an IE Repair? (I assume that that is possible
only because previous poster mentions IE55sp2 which means the OS
is not XP.)


Good luck

Robert Aldwinckle
---

I have loaded the 831167 patch, but that did not fix my problem in IE6. I uninstalled the patch, but it still will not let my

user recieve the authorization reply screen to tell her the credit card went through. I do not want to format this pc. Does anyone
know a workaround or is MS planning on putting out a fix for this problem?