286117 - Get an error code 500 (internal server error) message when I go to certain encrypted websites.

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[mwolff]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707

When I go to certain sites, especially financial sites (my banks), the page
comes up saying I have an "error Code 500" and that it is an internal server
problem. It also occurs when I go to sites where I need to log into get get int
that particular website. to view my accounts or purchase products (ie:
amazon.com, DVD planet.com, etc).

Reproducible: Always

Steps to Reproduce:
1. logged onto my isp server (Earthlink) where Firefox 1.0.01 is my default
web-browser
2.Go to favorites and try to log onto vaious sites ie: usaa.com, amazon.com, etc
3.When browsers go to those pages, a white page shows up saying that I have an
error code 500 which could be an internal server problem

Actual Results:  
Same as step number#3.

Expected Results:  
Should have gone to home page where it will ask that I use my user name and
password to log onto that site to have personal information or preferences for
myself. 

In firefox, I had been using the password manager to store and remember my logon
information. I am back using Mozilla 1.7 regular browser and e-mail and these
sites are working fine when I go to them and logon.

Comment 1

[Ben Fowler]

Your lizard is too old to report bugs against.

We will need the co-operation of the site admin to diagnose errors
of type 500.

Comment 2

[mwolff]

(In reply to comment #1)
> Your lizard is too old to report bugs against.
> 
> We will need the co-operation of the site admin to diagnose errors
> of type 500.

1) I do not understand when you say my lizard is to old to report bugs?
2) I am the site administrator of this pc and what type of cooperation do you
need from me? 

Comment 3

[mwolff]

Ben Goodger <[e-mail]>

First off, I answered in the comment plane when my mail page brought me to the
bugzilla site and therefore do not know if you got my reply. Second, I do
understand about my lizard being to old and what do I need to update it?
Finally, I am the owner of this PC and want to know how I can cooperate to get
this error message figured out or are you talking about the site managers of the
url pages I go to and get the error message?

Comment 4

[Ben Fowler]

(In reply to comment #2)
> (In reply to comment #1)
> > Your lizard is too old to report bugs against.
> > 
> > We will need the co-operation of the site admin to diagnose errors
> > of type 500.
> 
> 1) I do not understand when you say my lizard is to old to report bugs?

You give its date as 20040707; Bugzilla is really for reports of defects that
can be reproduced on build only a day or two old.

> 2) I am the site administrator of this pc and what type of cooperation do you
> need from me? 

Things like server logs what did the script report when it returned a '500
Internal Server Error'

Comment 5

[Nickolay_Ponomarev]

I'm really not sure what does it have to do with Firefox :-/
It's a /server/ error after all.

Comment 6

[Ben Fowler]

(In reply to comment #5)
> I'm really not sure what does it have to do with Firefox :-/
> It's a /server/ error after all.

At first blush how do we know that Firefox is sending a correctly
formatted request to the server? Could something in Firefox be
tickling a bug/edge case in the server?

Without further information (such as server logs) we can't dismiss this
quickly, can we?

I think it would be nice if there were a page in/near bugzilla where
information could be posted concerning how to handle some of these
reports which are likely to be non-bugs: DNS problems, Firewalls, Internal
Server Errors, Non-W3C javascript, Erroneous mime-types, character encoding.
A lot of erroneous behaviour on the web, and some normal behaviour looks
like a bug in the browser, and whilst it is unfortunate, it is hardly 
suprising that people come here. I think that what is needed is an agreed,
brief, courteous set of pointers to helpful resources (and out of Bugzilla).

See Bug 279696 "Please describe "what is bug" and "b.m.o is not Help center" 
in bug writing guidelines"

Comment 7

[Nickolay_Ponomarev]

You're right, from theoretical viewpoint this may be a bug in Firefox. However,
this bug report will not lead to a fix in Firefox code without server-side
information. No such information was provided for almost a month.

Comment 8

[Ben Fowler]

I fully agree with what you say and the way you put it. So, how long does one
wait before resolving the report as WORKSFORME (insufficent information/ no
response from reporter)?

Comment 9

[Nickolay_Ponomarev]

I myself think one month plus/minus a week is enough. If new information
appears, the bug can always be reopened.

Comment 10

[Carsten Book [:Tomcat]]

-> no reply

Resolved as WFM