223891 - submit form-based login authentication to a java appserver (tomcat) error

Status: RESOLVED EXPIRED

(Core :: DOM: Core & HTML, defect)

Description

[Adam Hardy]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031025
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031025

This is with 1.6a, & isn't a problem in 1.5. 

When I submit the login form in form-based authentication on a java server, the
server returns a Status 400. In 1.5 and in other browsers this would normally work. 

I assume it is a problem with handling redirects, since entering the wrong login
info results in a normal login error. 

So the server receives and processes the login, but on success, the redirect to
the originally requested page is getting lost or mixed up with something. 

Reproducible: Always

Steps to Reproduce:
1.try to access a page on a java appserver that is using normal HTTP non-SSL
form-based authentication security.
2.The login page appears
3.Enter correct login info & submit
4.Login is processed by server


Actual Results:  
User is redirected to a status 400 page 

Expected Results:  
User is redirected to the originally requested page

I've attached an HTTP debug log.

Comment 1

[Adam Hardy]

Attachment: http log

Comment 2

[Darin Fisher]

adam: thank you for the log file, but can you also submit a log for the same
session captured using mozilla 1.5 so we can see what a working version of the
log would look like?  thanks!

Comment 3

[Adam Hardy]

Attachment: this is the log from 1.5 (working).

After the login form ssllogin.html (which actually isn't currently being used
for ssl login) the page private/library.do should load.

Comment 4

[Adam Hardy]

No idea if this info is useful to you, but I just tried firebird for the first
time. It doesn't suffer this bug. 

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.