Very Computer

by **Douglas Melnik** » Wed, 21 Oct 1998 04:00:00

>> > I recently upgraded to Apache 1.3.3 from NCSA HTTPd and am having trouble
>> > getting my webpages to work properly. In particular, I have in my html
>> file
>> > lines like:

>> > <img SRC="gifs/redball.gif" ...>

>> > where gifs is a directory directly below the current directory. The NCSA
>> > server had no problem with this, but Apache 1.3.3 does not seem to
>> understand
>> > this.

>> Apache doesn't actually know the context of the request, the problem may
>> be related to redirects with incomplete directory names (/directory
>> instead of /directory/). In any case it will help if you check the error
>> log and see what the client actually tried to access (and possibly post
>> a probe from your logs and a fragment of failing HTML).

i agree that this could happen if the user was browsing to /directory instead
of /directory/ (that's fixable in srm.conf) but here, the user is browsing to
a fixed file.... i don't see why it wouldn't work.

- doug

---------------------------------------------------------
Doug Melniker
Center for Connected Learning and Computer-Based Modeling
Tufts University
www.ccl.tufts.edu

by **Marc Slemk** » Wed, 21 Oct 1998 04:00:00

>I recently upgraded to Apache 1.3.3 from NCSA HTTPd and am having trouble
>getting my webpages to work properly. In particular, I have in my html file
>lines like:
><img SRC="gifs/redball.gif" ...>
>where gifs is a directory directly below the current directory. The NCSA
>server had no problem with this, but Apache 1.3.3 does not seem to understand
>this.

Neither Apache nor NCSA understands such things. That is completely
up to the client. It will resolve the relative URL according to its
concept of what directory the document where the link is from is in.

by **Klaus Johannes Rusc** » Thu, 22 Oct 1998 04:00:00

> I recently upgraded to Apache 1.3.3 from NCSA HTTPd and am having trouble
> getting my webpages to work properly. In particular, I have in my html file
> lines like:

> <img SRC="gifs/redball.gif" ...>

> where gifs is a directory directly below the current directory. The NCSA
> server had no problem with this, but Apache 1.3.3 does not seem to understand
> this.

Apache doesn't actually know the context of the request, the problem may
be related to redirects with incomplete directory names (/directory
instead of /directory/). In any case it will help if you check the error
log and see what the client actually tried to access (and possibly post
a probe from your logs and a fragment of failing HTML).

Klaus Johannes Rusch
--

http://www.atmedia.net/KlausRusch/

by **UK - link, technical Services, Transc** » Fri, 23 Oct 1998 04:00:00

> >I recently upgraded to Apache 1.3.3 from NCSA HTTPd and am having trouble
> >getting my webpages to work properly. In particular, I have in my html file
> >lines like:

> ><img SRC="gifs/redball.gif" ...>

> >where gifs is a directory directly below the current directory. The NCSA
> >server had no problem with this, but Apache 1.3.3 does not seem to understand
> >this.

> Neither Apache nor NCSA understands such things. That is completely
> up to the client. It will resolve the relative URL according to its
> concept of what directory the document where the link is from is in.

Could this be a problem that would be resolved by putting an Alias in
one of the .conf files? I don't know NCSA, so I don't know if that works
the same as apache.

I have a line like the following in my httpd.conf:

Alias /gifs/ /whatever/your/path/gifs/

He only would have to use a leading / to get this to work then.

Kees Vonk

Very Computer

403 Error for relative paths in Apache 1.3.3

403 Error for relative paths in Apache 1.3.3

403 Error for relative paths in Apache 1.3.3

403 Error for relative paths in Apache 1.3.3

403 Error for relative paths in Apache 1.3.3