Hello.
By the way, do you have the setting enabled to use the Host header used to
switch NameVirtualHost during TLS negotiation?
I don't know how to do that since the Japanese documentation is rarely updated
:)
Were those things implemented?
Regards.
Hello.
Frank Gingras wrote on 2023/10/17 02:22:
> That's just multiviews.
For that matter, do everyone else do multiviews?
What if we simply name the file b, and then do the following?
SetHandler php-script
# If it works via CGI as well.
SetHandler cgi-script
Regards.
Hello.
Do I have to keep attaching png named jpg here? :)
According to that png or jpeg or whatever it is, it still has .
That means the following pattern will pass, right?
D:\path\to\dir
D:/path/to/dir
\\hostname_or_ipaddress\path\to\dir
//hostname_or_ipaddress/path/to/dir
Regards.
Dave Wreski wrote on 2023/04/12 01:39:
> In case I wasn't clear, simply removing the caret was not enough to make this
> work. The "Require env SOMENAME2" was enough to begin blocking every page on
> the site with a 403, not just the RSS feeds or the bots, but every legitimate
> request.
>
>
Hello.
Frank Gingras wrote on 2023/04/11 13:36:
> The legacy authz directives from 2.2 will indeed cause issues when mixed
> with Require (2.4). Do not mix them.
Yes.
Basically, they MUST NOT BE MIXED, but we should know how they behave when the
mod_access_compat is loaded.
I think it was like
Dave Wreski wrote on 2023/04/11 10:54:
> SetEnvIf user-agent "(?i:TurnitinBot)" stayout=1
> SetEnvIf Request_URI "^linuxsecurity_features\.*$" !stayout
I have done it in the past, too.
It was like allowing another level of conditions to be attached to Allow and
Deny, depending on the condition
Hello.
I don't know what is troubling you...
For now, don't use the combination of Order,Allow,Deny and Require* in
configuration file that will be created in 202x. :)
AllowDeny of ENV should be replaced by the following.
Allow from env=X_FOOBAR -> Require env X_FOOBAR
It can write more
Hello.
While it is important to look at the error logs, this may not have led to a
situation where the proper error logs are output :)
First, make sure they edit the appropriate config files and also make sure they
are rebooting the appropriate server processes.
For example, they could write
Hello.
I understood why everyone was having a hard time :)
With the default log level, no error log seems to be written in case of a 404
error.
As far as that access log is concerned,
Does teacherregister.php exist in /var/www/html ?
If so, do /var/www/html/javascript/*.js exist?
We would like
Frank Gingras wrote on 2021/03/20 09:46:
> It has nothing to do with being "free to do anything".
>
> This is about basic security, and the principle of least privileges.
However, a directory with permissions of 0755 (rwxr-xr-x) on FreeBSD behaves
the same as a Linux directory with permissions
Frank Gingras wrote on 2021/03/19 21:36:
> This is an extremely bad idea. You should never write to the docroot from
> your application. Write outside the docroot instead, and use group write
> permissions.
Isn't root the owner of docroot?
When the user of an application is the owner, he should
I'm not sure, but FreeBSD happens to be different from Linux, so please change
the directory group to www as well.
Permissions of 700, 750, 755, 770 or 775 should be sufficient.
-
To unsubscribe, e-mail:
In most cases, mod_asis in httpd.conf will probably remain commented out.
Everyone's favorite :), mod_cgi and mod_cgid, will be set to use it.
Both mod_asis and mod_cgi use ap_scan_script_header_*, so the response code
will change depending on the Status header.
The special consideration of the
Brandon Helsley wrote on 2021/01/06 10:02:
> I'm trying to open the web interface for poudriere on FreeBSD and have
> copied the sample configuration file into the includes directory. I haven't
> made any changes to this configuration file or the httpd.conf file yet. I'm
> not sure which
I have added
xml2EncDefault UTF-8
directive with something wrong when combining xml2enc_module and
proxy_html_module.
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail:
300 and 399, the URL argument must be present. If
the status is not between 300 and 399, the URL argument must be omitted.
Perhaps, it needs a fix. I have already used a patch attached to 2.4.x-dev.
Regards.
--
Tatsuki Makino tatsuki_mak...@hotmail.com
patch-2.4.x-r1670805-mod_alias.c
16 matches
Mail list logo
