Hi list,
I have a server {} block that is protected with auth_request; on the top level.
auth_request is used for a interactive login process.
I have some endpoints that will receive data from other software, and
must instead be protected by auth_basic. However, "auth_request off;"
is ignored in
This is my current vhost for the webdav access on the nginx rev. proxy:
[..]
If I switch the vhost to listen on port 80 without ssl, everything is
fine and files can be renamed or moved via webdav.
If it works on http but not with ssl it might indicate that either this
configuration part doe
Hi,
I've installed nginx as a reverse proxy in front of an apache webdav
server. Everything seems to be OK so far, but renaming or moving files
failes.
This is my current vhost for the webdav access on the nginx rev. proxy:
server {
listen 443 ssl;
server_name
"~^(?(webdav|schulweb))\-ca(
If your server gets hacked due to a single website, you have bigger problems,
and mod_security won’t fix the issue.
Consult with security professionals or give the task of managing your
infrastructure to someone that can properly secure the environment.
On 12/10/2017, 13.26, "nginx on behalf of
You are right. I didn't know what canonical url:s where, but now I know. Yes
there is in fact two servers. One server is running Apache with a website
that has maybe 10 different DNS-domains pointing to it and then there is
another server running IIS with lots of websites but usually only one
DNS-d
Sounds like the problem is that you don’t have nginx configured to enforce
canonical urls.
What do I mean by this?
Imagine that every page on the site has one and only one “correct URL”
So someone might type
http://www.mydomain.com
http://mydomain.com
http://www.mydomain.com/index.html
and
I found the solution, but I don't understand what it does. When I add:
proxy_cache_key "$host$uri$is_args$args";
To a location block it magically works. I have no clue what happens, it was
just a snippet I found on the Internet used by some other guy setting up a
reverse proxy with cache.
And th
Thanks for the help, and I have found the solution now, so I will post it in
this thread.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,276670,276832#msg-276832
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinf
I believe that there is sometimes a problem with the cache when i connect
through a private IP-address instead of always using the public address.
Since I started to always use the public address and a hairpin-nat, it
always works. Maybe the cache has a problem when seeing me coming from
different
