403 Error for relative paths in Apache 1.3.3

403 Error for relative paths in Apache 1.3.3

Post 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

 
 
 

403 Error for relative paths in Apache 1.3.3

Post 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.

 
 
 

403 Error for relative paths in Apache 1.3.3

Post 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/

 
 
 

403 Error for relative paths in Apache 1.3.3

Post 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

 
 
 

1. Apache error: 403 Forbidden by Rule

Folks,

I have configured ( for the first time) an Apache server on a Solaris
server.  All seemed to go well, however, I receive the following errors
in my /logs/error.log file:

        [Thu Dec  5 14:53:59 1996] setgid: Invalid argument
        [Thu Dec  5 14:53:59 1996] - unable to set group id

I browsed the httpd.conf file and modified the Group parameter to
match the gid of nobody (in our case 60001), but this did not help.
I'm guessing this is where the problem exists based on the error
message.

Probably related, when I attempt a connection to the server, I receive
the following error from the browser:

        Error 403
        Forbidden - by rule

The online docs and the FAQ did not reveal the answer.  Could someone
lead me in the general direction.

Thanks!
Scott

2. HELP!!. mksysb

3. 403 Error on the Apache web server on a solaris box during busy hours.

4. FreeBSD 2.1.5 Install

5. Newbie gets Error 403 from Apache 1.3.12 on Linux

6. #if defined .... some problems....

7. 401 or 403 Apache Custom Error

8. setting up X windows

9. Apache V1.3.3. Error 403

10. Error 403 Forbidden! and Apache/php4

11. Apache error 403

12. 403 Forbidden Error on Apache

13. Apache + 403 error on DocumentRoot