> >     I generally suspect some kind of encoding issue with how IE6/XP is
> > setting up the POST (broken encoding?), and/or how qmailadmin
> > interperts it, or a problem in IE and how it maintains session data
> > perhaps?
> >
> >     I've seen that this has been discussed in the list archives, to no
> > resolution.  I put forth the above as additional information, hoping
> > that some resolution can be found.  Any additional information from
> > myself regarding this problem, I will be happy to provide if someone
> > will just ask what they need to know.
>
> Can you install Ethereal (or another packet sniffer) on the computer
> that consistently experiences the problem, and capture the session for
> me to review?  We'll be able to see the requests that WinXP makes, and
> the responses that the server sends.  Provide a list of what you did in
> QmailAdmin to bring on the bug as well.

        Well, I'll have to setup a non-SSL'd webserver with qmailadmin,
and track down a client who's having this problem, but yeah, I can
probably get this done.

        As far as what was done in qmailadmin to bring on the bug, when
clicking to change screens (ie: to go from main to add user) are GET
requests; these have never been a problem.  Whenever a client tries to
say, add a user, the form is submitted as a POST instead of a GET.  At
this point, it fails.  So, according to what I have gathered by
corrolating the apache logs and the clients complains, any major operation
in qmailadmin which sends a POST fails - but not 100% of the time, only
like 95% of the time.

        Anyway, I'll get back to you once I've got a cleartext webserver
setup and a client who can duplicate the problem (I can't duplicate it
myself - I don't have an XP box to test with).

-- 
Jack
-------------------------------------------------------------------------------
When man calls an animal "vicious", he usually means that it will attempt to
defend itself when he tries to kill it.
-------------------------------------------------------------------------------

Reply via email to