You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by "Mark A.Horstman" <ma...@sbc.com> on 2001/01/31 17:41:17 UTC

general/7167: extra path information and the end of a URL is causing relative paths within the document to be wrong

>Number:         7167
>Category:       general
>Synopsis:       extra path information and the end of a URL is causing relative paths within the document to be wrong
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Jan 31 08:50:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     mark.horstman@sbc.com
>Release:        1.3.17
>Organization:
apache
>Environment:
SunOS sarek 5.6 Generic_105181-21 sun4u sparc SUNW,Ultra-2
cc: WorkShop Compilers 5.0 98/12/15 C 5.0
Apache/1.3.17 (Unix) mod_perl/1.25
>Description:
directory structure:
	/images/test.gif
	/foo/bar.html

bar.html source:
	<HTML>
		<HEAD><TITLE>foobar</TITLD></HEAD>
		<BODY><IMG SRC="../images/test.gif></BODY>
	</HTML>


http://server/foo/bar.html
	bar.html is displayed, image is displayed

access.log entry:
	[31/Jan/2001:10:24:14 -0600] "GET /foo/bar.html HTTP/1.1" 200 121
	[31/Jan/2001:10:24:14 -0600] "GET /images/test.gif HTTP/1.1" 304 -

http://server/foo/bar.html/glitch
	bar.html is displayed, image is not displayed

access.log entry:
	[31/Jan/2001:10:24:19 -0600] "GET /foo/bar.html/glitch HTTP/1.1" 200 121
	[31/Jan/2001:10:24:19 -0600] "GET /foo/images/test.gif HTTP/1.1" 404 308

If the server can figure out where/what the real document is (/foo/bar.html), shouldn't it be be able to resolve relative paths correctly?
>How-To-Repeat:
see full description.

Sbehaviour was observed on Apache/1.3.14 (Unix) mod_perl/1.24.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]