Closed Bug 81376 Opened 23 years ago Closed 22 years ago

Categories

(Tech Evangelism Graveyard :: Danish, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bugzilla, Assigned: tristan)

References

()

Details

(Whiteboard: [BANKING][SYNTAX-HTTP][eurocontest])

If you go to:
http://www.danskebank.dk/DanskeNetbank
the upper left frame shows a "Error 500"

build 20010516

The frameset renders ok in both IE and NS but not in Moz.
Indeed, works for me in IE5 but gives under Mozilla build 2001-05-13-08 gives:

Error 500
HTTP Web Server: Unknown Command Exception
Lotus-Domino Release 5.0.5

OK, loading the actual frame URL 
http://www.danskebank.dk/DK/web.nsf/menuhtml?OpenView&04&RestrictToCategory=04
works fine.

The frameset on the main page has an onLoad property which calls a Javascript
function in the page in question, "menukald()". So I would guess that the 
problem is a Javascript one?
actually I first thought that the problem was the "\" in the url in the 
frameset.
Henrik - I don't think so. I just wrote a Proxomitron rule to swap any backslashes
for forward slashes, and reloaded the page (so Mozilla would never see the "\"),
and got exactly the same behaviour.

I tried saving the frames page to disk and adding a BASE HREF and that also works.
qa to me. 

A 500 error is a server side error, so we might be sending them something
strange in the context putting the frame in the larger page, or they might be
messing something up on their end.

One method of further analyzing this would be to do a packet trace. I'm marking
this qawanted.
Keywords: qawanted
QA Contact: tever → benc
Target Milestone: --- → mozilla0.9.2
Probably caused by the "&04&" (which is invalid HTML). Might be Evangelism.
Andreas.. seems not. I tried a Proxomitron rule to get rid of that (so the 
source was "dk\web.nsf/menuhtml?OpenView&RestrictToCategory=04", rather than
"dk\web.nsf/menuhtml?OpenView&04&RestrictToCategory=04", but it still failed in
exactly the same way. :-(

Aha!! A bit more digging, and I think I've found something!! OK, here is the
outgoing request from Mozilla:

+++GET 76+++
Using Proxy - dsproxy2:80
GET http://www.danskebank.dk/DK/web.nsf/dk/web.nsf/menuhtml?OpenView&04&RestrictToCategory=04 HTTP/1.0
Connection: keep-alive
Host: www.danskebank.dk
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)
Accept: text/xml;q=1, text/html;q=0.9, image/png;q=1, image/jpeg;q=1, image/gif;q=0.9, text/plain;q=0.8, text/css;q=1, */*;q=0.01
Accept-Language: en
Accept-Charset: ISO-8859-1, utf-8; q=0.667, *; q=0.667
Cookie: cookon=true; statcookcommon=SessionID%3C20010524085859487626%3ESessionTimestamp%3C990691389915%3Eremote_addr%3C159.104.224.21%3Ehttp_via%3C1.0%20DSPROXY6%3Eversion%3C01.018%3EMachineID%3C2001051710564660840846%3ELogCount%3C5%3ELogEntry01%3C20010524085859%23www.danskebank.dk/danskenetbank%2304%23Danskebank.dk/Netbank/Forside%23www.mmjp.or.jp/knife/%23endtime%3B%3ELogEntry02%3C20010524090037%23www.danskebank.dk/danskenetbank%2304%23Danskebank.dk/Netbank/Forside%23www.mmjp.or.jp/knife/%23endtime%3B%3ELogEntry03%3C20010524090110%23www.danskebank.dk/danskenetbank%2304%23Danskebank.dk/Netbank/Forside%23www.mmjp.or.jp/knife/%23endtime%3B%3ELogEntry04%3C20010524090143%23www.danskebank.dk/danskenetbank%2304%23Danskebank.dk/Netbank/Forside%23www.mmjp.or.jp/knife/%23endtime%3B%3ELogEntry05%3C20010524090309%23www.danskebank.dk/danskenetbank%2304%23Danskebank.dk/Netbank/Forside%23www.mmjp.or.jp/knife/%23endtime%3B%3E; cookses=true
Referer: http://www.danskebank.dk/DK/web.nsf/dk/web.nsf/menuhtml?OpenView&04&RestrictToCategory=04

(don't worry about the User-Agent saying IE, that's the Proxomitron faking it)

And here are the requests from IE 5.0:

+++GET 49+++
Using Proxy - dsproxy2:80
GET http://www.danskebank.dk/dk/web.nsf/menuhtml?OpenView&04&RestrictToCategory=04 HTTP/1.0
Connection: keep-alive
Accept: */*
Referer: http://www.danskebank.dk/dk/web.nsf/menuhtml?OpenView&04&RestrictToCategory=04
Accept-Language: en-gb
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)
Host: www.danskebank.dk
Cookie: cookses; cookon; cookon=true; statcookcommon=SessionID%3C20010517103503484285%3ESessionTimestamp%3C990093025996%3Eremote_addr%3C159.104.224.21%3Ehttp_via%3C1.0%20DSPROXY6%3ELogCount%3C5%3Eversion%3C01.018%3EMachineID%3C2001051710502673542496%3E
Connection stored: 48
Connection Reused: 48->49

Notice the difference? Mozilla is getting the URL wrong!!

Can someone tell if this might be involved ->

<script language=javascript>
   d=document.domain;
   while(d.indexOf(".")!=d.lastIndexOf("."))
   {
      d=d.substring(d.indexOf(".")+1)
   };
   document.domain=d;
</script>

..that's a chunk of script from the main page, before the frameset that is going
wrong..
I told you it was 500 was the correct server error :)

-qawanted (David, when you solve mysteries, you get to remove the keyword if you
think you solved it...)

If this is a JS problem, what component should we send it to?
Keywords: qawanted
This is not a js problem. Try turning of javascript for navigator and go to the 
page again. Same problem.....
David, can you turn off javascript and do the same network analysis as before?

If we are sending two different requests, we need to find the root cause.
Hi Benjamin,

With Javascript off, I get exactly the same thing:

+++GET 6+++
Using Proxy - dsproxy2:80
GET http://www.danskebank.dk/DK/web.nsf/DK/web.nsf/menuhtml?OpenView&04&RestrictToCategory=04 HTTP/1.0
Connection: keep-alive
Host: www.danskebank.dk
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)
Accept: text/xml;q=1, text/html;q=0.9, image/png;q=1, image/jpeg;q=1, image/gif;q=0.9, text/plain;q=0.8, text/css;q=1, */*;q=0.01
Accept-Language: en
Accept-Charset: ISO-8859-1, utf-8; q=0.667, *; q=0.667
Keep-Alive: 300
Cookie: cookon=true; statcookcommon=SessionID%3C20010525165216683563%3ESessionTimestamp%3C990806061600%3Eremote_addr%3C159.104.224.21%3Ehttp_via%3C1.0%20DSPROXY6%3Eversion%3C01.018%3EMachineID%3C2001051710564660840846%3ELogCount%3C4%3ELogEntry01%3C20010525165216%23www.danskebank.dk/danskenetbank%2304%23Danskebank.dk/Netbank/Forside%23www.mmjp.or.jp/knife/%23endtime%3B%3ELogEntry02%3C20010525165257%23www.danskebank.dk/danskenetbank%2304%23Danskebank.dk/Netbank/Forside%23www.mmjp.or.jp/knife/%23endtime%3B%3ELogEntry03%3C20010525165346%23www.danskebank.dk/danskenetbank%2304%23Danskebank.dk/Netbank/Forside%23www.mmjp.or.jp/knife/%23endtime%3B%3ELogEntry04%3C20010525165421%23www.danskebank.dk/danskenetbank%2304%23Danskebank.dk/Netbank/Forside%23www.mmjp.or.jp/knife/%23endtime%3B%3E
Referer: http://www.danskebank.dk/DK/web.nsf/DK/web.nsf/menuhtml?OpenView&04&RestrictToCategory=04

(don't worry about the User-Agent saying IE, that's the Proxomitron faking it)
Hang on, just looking a little closer, maybe this is a clue:

Here is the response to the initial request, i.e. for the main page
http://www.danskebank.dk/DanskeNetbank that the problem frame is located on.

+++RESP 38+++
HTTP/1.1 200 OK
Via: 1.0 DSPROXY6
Proxy-Connection: Keep-Alive
Content-Length: 2081
Content-Type: text/html
Server: Lotus-Domino/5.0.5
Date: Wed, 30 May 2001 07:51:55 GMT
Content-Base: http://www.danskebank.dk/DK/web.nsf/FrameDef?readform&DanskeNetbank
Expires: Tue, 01 Jan 1980 06:00:00 GMT
Pragma: no-cache

..now I don't know much about HTTP, but that Content-Base: line has the path
that our frame address is being (wrongly) appended to. And [On Holiday] said
that he "tried saving the frames page to disk and adding a BASE HREF and that
also works".

So.. could that be it? And if so, is it our fault or theirs? :-)
Content-Base is not defined in RFC 2616, but was in RFC 2068. If we choose to
support Content-Base, we do the right thing here. It's their fault.
gagan: ->evangelism
Assignee: neeti → bclary
Component: Networking: HTTP → Evangelism
QA Contact: benc → zach
Whiteboard: [BANKING][SYNTAX-HTTP]
Priority: -- → P4
moving target milestone to 0.9.3
Target Milestone: mozilla0.9.2 → mozilla0.9.3
-> Intl
Assignee: bclary → nitot
QA Contact: zach → momoi
Status: NEW → ASSIGNED
Priority: P4 → P3
moving target milestone to 0.9.4

Accepting bug.

Changing priority to P3 (major blockage to a non-partner site).
_REALLY_ changing priority to 0.9.4 :-)
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Component: Evangelism → European
Product: Browser → Tech Evangelism
Target Milestone: mozilla0.9.4 → ---
Version: other → unspecified
Moving to new component "West Europe".  European component is being removed. 
See bug 95808 for details.
Status: ASSIGNED → NEW
Component: European → West Europe
QA Contact: momoi → caillon
http://www.bgbank.dk/bgnetbank has the exact same error, but since the two
companies have merged, the sites was probably done by the same bureau.

Another thing "bugging" me is that you can't actually log on with mozilla, but
that's a bug thats very hard to reproduce. Since i have absolutely no idea
what's causing this, i won't file it.
*** Bug 94096 has been marked as a duplicate of this bug. ***
Blocks: 124594
Mozilla doesn't support the Content-Base header anymore (see bug 94096), so this
problem is fixed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Whiteboard: [BANKING][SYNTAX-HTTP] → [BANKING][SYNTAX-HTTP][eurocontest]
v20020325
Status: RESOLVED → VERIFIED
resolved euro west non-.com url bugs to other
Component: Europe: West → Other
Component: Other → Danish
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.