107419 - Problem using p4web

Status: RESOLVED FIXED

(Core :: Networking: HTTP, defect)

Description

[Louis Kruger]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012
BuildID:    2001101201

I'm using the Perforce P4web tool, which provides an HTML interface to Perforce.
 When I point my browser at the perforce server using Internet Explorer or
Netscape 4.7, I am redirected to the following URL and the interface works as
expected:

http://localhost:5503/@md=c&cd=//&c=gud@//?ac=83

Using Mozilla, I am sent instead to this URL:
http://localhost:5503/%40md=c&cd=//&c=BAw%40//?ac=83
and instead of listing my perforces workspaces, I get the following message:

Unintelligible revision specification 'md=c&cd=//&c=BAw@//*'.

It looks like Mozilla is handling the "@" character in the URL differently from
IE or Netscape 4.

Reproducible: Always
Steps to Reproduce:
1.  Install p4web from www.perforce.com
2.  Run p4web.
3.  Point Mozilla at the p4web server.

Actual Results:  See description

Expected Results:  See description

Comment 1

[timeless]

.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Over to networking:http.  This is a URI parser issue, not HTML parser.

Comment 3

[Darin Fisher]

Yup, RFC2396 section 3.3 explicitly allows the '@' character in a URL path
segment.  It does not require this character to be escaped.

cc'ing andreas... andreas: do you agree?  do you want to own this bug?

Comment 4

[Andreas Otte]

taking ...

Right, it is not necessary to escape @ in the directory part, but it is an error
in p4web to not being able to handle it. We can escape every character inside
every url component as long as it is not used for url syntax. 

But, we already have taken steps to help out here. See bug 108575 for details,
just put an r= on the latest patch and it will go forward ...

Comment 5

[Andreas Otte]

fix for bug 108575 is checked in, this problem is history ...