Hi,
Am 05.10.2017 um 12:53 schrieb Michael Hekeler:
I don't need them I have them on a older system were apache 1.3 was
the standard webserver for openbsd still. So I simply want to
migrate the content to a system with a new standard webserver httpd.
Okay
But keep in mind that httpd is not Apa
> I don't need them I have them on a older system were apache 1.3 was
> the standard webserver for openbsd still. So I simply want to
> migrate the content to a system with a new standard webserver httpd.
Okay
But keep in mind that httpd is not Apache and converting complicated
htaccess stuff is
Hi,
Am 05.10.2017 um 10:11 schrieb Michael Hekeler:
And 2nd question would be how to give the user a way to implement
something like it on there own? I was thinking of a simply standard
include in the server definition but this might mess things up
if you need directory specific and user defin
> And 2nd question would be how to give the user a way to implement
> something like it on there own? I was thinking of a simply standard
> include in the server definition but this might mess things up
if you need directory specific and user define-able override files like
those .htaccess then w
On 03.10.17 15:10, rosjat wrote:
Hi there,
I was wondering if there is some guidence out there for this sort of
thing? I know it's possible to simply block directories or put basic
auth in front of it but what's about some more fine grained stuff for
a file in a directory? Like this
or
Hi there,
I was wondering if there is some guidence out there for this sort of
thing? I know it's possible to simply block directories or put basic
auth in front of it but what's about some more fine grained stuff for a
file in a directory? Like this
order deny,allow
deny f
6 matches
Mail list logo
