403 Forbidden during updating Apache 1.2 to 1.3b3

403 Forbidden during updating Apache 1.2 to 1.3b3

Post by Marc Slemk » Thu, 23 Apr 1998 04:00:00




>Hi
>I just update apache from 1.2.0 to 1.3b3, and I have insert in the conf file
>the addign line between the 2 versions.

Erm... I strongly recommend against running old betas, but upgrading
to old betas is even worse.  1.3b6 is out.

Quote:>After this, I can't see the main page of my server ....
>I verify the SMR.CONF / ACCESS.CONF and found nothing.
>I have an error in the /logs/error_log like this :
>[crit] (6)Device not configured : /.htaccess pcfg_openfile: unable to check
>file, ensure it is readable

This means it gets a "device not configured" error when it tries
to open /.htaccess.  Do you have some odd setup where attempts
to open /.htaccess don't fail but instead return a device not cofigured
error?

As a workaround, you can do something like:

<Directory />
AllowOverride none
</Directory>

...then you need to be sure you have explicit settings for where you
want to be able to use htaccess files.  Setting AllowOverride none
stops Apache from looking for htaccess files and therefore stops
this from occuring.

 
 
 

403 Forbidden during updating Apache 1.2 to 1.3b3

Post by Marc Slemk » Fri, 24 Apr 1998 04:00:00



>> Erm... I strongly recommend against running old betas, but upgrading
>> to old betas is even worse.  1.3b6 is out.
>yes but the AMiga version is to 1.3b3

Well it would help if you mentioned this detail.  That is not Apache
per say, but some version of Apache modified by someone to work on
some other platform.

Quote:

>> >[crit] (6)Device not configured : /.htaccess pcfg_openfile: unable to check
>> >file, ensure it is readable

>> This means it gets a "device not configured" error when it tries
>> to open /.htaccess.  Do you have some odd setup where attempts
>> to open /.htaccess don't fail but instead return a device not cofigured
>> error?
>My setup work correctly with the 1.2 version ... I have some directories with
>different rights access for different users ... My old configuration work
>fine, and I have not error report in /log/error_log
>What is the real difference in the security between the 1.2 and 1.3 version ??
>I don't find this solution in the web site ...

There are no solutions to Amiga problems because Apache doesn't
run on the Amiga.

There is no description of this solution because it isn't a problem
on the OSes that Apache runs on.  I have no idea what is happening
on your Amiga to make it an issue; the change is just a workaround
to some other problem.

 
 
 

1. 403 forbidden error with apache when symlinking to different partition

I have separate partition which has the document root for apache on it
and all the websites and it's mounted under /w3. Recently I have been
running out of space and wanted to move the website to the home
directory /home/mj/web and I made a symlink from its original location
to /home/mj/web but I get a 403 error and in the error log it says
"Symbolic link not allowed".

I have no problem symlinking within the /w3 partition but you can't
symlink outside. I would love to be able to move the files to the
different partition so I can free space on the /w3 partition.

I seem to be the only one with this problem ever because I searched
Google for a solution and I can't seem to find any information.

So I hope some Apache guru will be able to help me with this.

2. Int.Modem can't dial out to PPP connection

3. Apache 1.3.19 return 403 Forbidden on PDF file

4. AppleTalk support

5. apache user dirs 403 forbidden w/redhat 5.0

6. COFF support for ld?

7. Apache / 403 Forbidden

8. Problem upgrading libc (ELF)

9. H: Debian 2.0r3 LINUX: Apache: CGI scripts: 403 - access forbidden

10. Annoying Error! Apache: 403 Forbidden

11. Apache 403/forbidden error

12. Apache error "403 Forbidden access to /~user/"

13. 403 Forbidden Message on Apache 1.3.9