> I always get 403 Forbidden for that.
I can recall when I first downloaded one of these web servers , if you put
an incorrect url for which a pages didn't exists your directory structure
appeared with full http access to anyone.
Clearly the restriction on /tmp is an improvement.
On Wed, 1
I remember I have provided them in my first email. The server had only 3 lines
of log except startup information.
> [authz_core:debug] [pid 4469:tid 140408108734144] mod_authz_core.c(815):
[client 127.0.0.1:37804] AH01626: authorization result of Require all denied:
denied
> [authz_core:debu
> ErrorLog entry:
I mean the contents of the log.
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
It works fine for /tmp itself, but says 403 for any directories under
/tmp, regardless of their permissions (neither 777 nor 1777 works)
All directories are owned by root and root group
ErrorLog entry:
> ErrorLog "/var/log/httpd/error_log"
>
> LogLevel debug
>
>
> #
> # The followin
Hello,
I am not sure that the answer is correct. I briefly tried to set up
Apache/2.4.55 with /tmp as you described and it seems to work fine. Are you
sure that there is no issue with permissions in subdirectories/files
themselves?
Regards,
On Wed, Feb 15, 2023 at 4:06 PM accelerator0099
wrote
> Except for anything under /tmp.
>
> I always get 403 Forbidden for that.
>
What's the verbatim ErrorLog entry for it?
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@http
That's for serving temporary files, of course.
I am developing a file-sharing web application, but it hasn't finished
yet. Before finishing it if I upload something to or download something
from the server those files are stored in /tmp. In most cases they are
just temporary files and should
On Wednesday 15 February 2023 at 15:21:58, accelerator0099 wrote:
> Apache is unable to access /tmp in any way.
> I always get 403 Forbidden for that.
> Why is /tmp different from others?
My guess (and it is one) is that since /tmp can be written to by any user,
this is a security feature whic
This problem happened in a recent apache release before version 2.4.55.
I encountered this after a system upgrade a month ago.
Apache is unable to access /tmp in any way.
We may let apache host some external websites by:
Alias "/ext" "/path/to/external"
Options Indexes
Require
