Closed Bug 25976 Opened 25 years ago Closed 25 years ago

Can't login to excite webmail

Categories

(Core Graveyard :: Security: UI, defect, P3)

1.0 Branch
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: jeellis, Assigned: edburns)

References

()

Details

(Keywords: top100)

Using M13 (and M12 as well) when trying to login to Excite Inobox mail using a form interface, an error is returned. The resulting page says that the server may be too busy, but it loads this error page repeatedly when using Mozilla, but loads fine with other browsers used at the same time. Win 98 release is the original release with all updates and patches installed.
Also happens on Linux build 2000.01.31.14. To reproduce: 1. Go to http://inbox.excite.com 2. Sign in as "_mozilla" with password "mozilla" Actual result: error page "Request Failed" Expected result: excite inbox opened. Don't think this is a forms problem. Maybe cookies?
Assignee: karnaze → morse
Component: Form Submission → Cookies
OS: Windows 98 → All
QA Contact: ckritzer → tever
Hardware: PC → All
Summary: Form submission does not work → Can't login to excite webmail
Status: NEW → ASSIGNED
Target Milestone: M14
The following comment is embedded in the Error Page: <!-- Exception ID: 244.20000202212348.3872.114759332 java.lang.Exception: unknown security component at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Compiled Code) at java.lang.Throwable.<init>(Compiled Code) at java.lang.Exception.<init>(Compiled Code) at excite.mex.MexURL.parseSecurityComponent(Compiled Code) at excite.mex.MexURL.parse(Compiled Code) at excite.mex.FolderViewerURL.parse(Compiled Code) at excite.mex.FolderViewerURL.<init>(Compiled Code) at excite.mex.FolderViewer.parseURL(Compiled Code) at excite.mex.MexPage.setMyRequest(Compiled Code) at excite.mex.MexPage.setRequest(Compiled Code) at excite.esp.PageDispatcher.handleRequest(Compiled Code) at excite.esp.PageDispatcher.service(Compiled Code) at javax.servlet.http.HttpServlet.service(Compiled Code) at com.sun.web.core.ServletWrapper.handleRequest(Compiled Code) at com.sun.web.core.Context.handleRequest(Compiled Code) at com.sun.web.server.ConnectionHandler.run(Compiled Code) Date: Wed Feb 02 21:23:48 PST 2000 Version: ExciteMail r170, ESP unknown Username: null UID: = Remote Address: 63.194.82.58 Brand: null Request URI: /ExciteMail/folder/rs=3D44409;check=3Dtrue/folder.html Request Headers: = Host: inbox.excite.com User-Agent: Mozilla/5.0 [en-US] (Linux; I) Accept: */* Accept-Language: 0 Referer: http://www.excite.com/u?hez cookie: mesp_popup=3Dy2k%3Dyes%26regpop%3Dno; MLUID=3DCZ8XaG+8RcFUBFDERQ= QcUq; popup=3Dno; CPL_SPLASH=3D1; UID=3D46672302DD0C2B0E; TKT=3Du46672302= DD0C2B0E.b38990CD0.r38990fe1.nx21VEMLSBge.fCgzW.cA01068E0.k1_0.pG0kNqJEtr= oC.mtnekEGFQt7mCCG; mexf=3D244.80.46672302DD0C2B0E -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-= +-+ -->
Adding pollmann to cc list. Could you try the same trick as in bug 26117 and see if this is also a "missing trailing slash in the referer tag" problem, and if so, mark this as duplicate? Also, I no longer think this is cookies, so please reassign to likely person.
Yes, I agree, it doesn't look like a cookie problem. I just never had a chance to prove conclusively before handing it off to someone else. But based on your comments above, I will hand this off to Gagan.
Assignee: morse → gagan
Status: ASSIGNED → NEW
Component: Cookies → Networking
Seems to work now. jeellis, can you check, too?
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Still doesn't work for me - cleared all cache and cookies, restarted and received a login error just as before.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Sorry, my latest problems were due to outdated build....this bug seems to have been resolved.
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
Ok, now it's broken again. Now the error page says: java.lang.Exception: invalid MexURL security component encoding So maybe it's a problem with getting security information from Mozilla. (Note: I can get to my inbox in Lynx, so it's not a matter of MISSING security; there are also no https: links in the form, etc.)
Status: VERIFIED → REOPENED
Component: Networking → Security: Crypto
Keywords: top100
Resolution: FIXED → ---
Reassign to security component.
Assignee: gagan → dougt
Status: REOPENED → NEW
QA Contact: tever → junruh
ed, can you look at this?
Assignee: dougt → edburns
This seems to be working again in Linux build 2000.03.15.09. jeellis, can you try this with a windows build?
Seems to be fine for me on latest win build.
Status: NEW → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → WORKSFORME
I second the WORKSFORME resolution. I've tried it with a beta1 branch build, with kestrel RC1 and Stanley's Java Plugin from 03/13/00. It works.
Still fine with today's linux trunk build.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: M14 → ---
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.