RE: Prevent Arbitary HTTP Host header in nginx

2020-02-27 Thread Reinis Rozitis
> I have added the below server block in /etc/nginx/nginx.conf > (https://paste.centos.org/view/raw/d5e90b98) > > server { > listen 80; >server_name _; >return 444; > } > > When i try to run the below curl call, I am still receiving 200 OK response. > #curl --verbose --h

Re: Prevent Arbitary HTTP Host header in nginx

2020-02-27 Thread Kaushal Shriyan
On Fri, Feb 28, 2020 at 1:21 AM Reinis Rozitis wrote: > > Is there a way to prevent Arbitrary HTTP Host header in Nginx? > Penetration test has reported accepting arbitrary host headers. Thanks in > Advance and I look forward to hearing from you. > > You can always define "catch all" server block

Re: Nginx location - Distinguish requests by arguments or queries

2020-02-27 Thread Francis Daly
On Thu, Feb 27, 2020 at 02:20:45PM -0500, stmx38 wrote: Hi there, > 1. "~*" to be "~^" > The first one looks like Nginx regexp we can use for locations, but the > second one not (^~): "map" is documented at http://nginx.org/r/map "~" means "this arg is a regex, not a string". "~*" means "and th

RE: Prevent Arbitary HTTP Host header in nginx

2020-02-27 Thread Reinis Rozitis
> Is there a way to prevent Arbitrary HTTP Host header in Nginx? Penetration > test has reported accepting arbitrary host headers. Thanks in Advance and I > look forward to hearing from you. You can always define "catch all" server block with: server { listen 80 default_server; s

Re: Nginx location - Distinguish requests by arguments or queries

2020-02-27 Thread stmx38
Hello Francis, It seems that your solution working as expected and I have started to test it. Also, have some questions here: 1. "~*" to be "~^" The first one looks like Nginx regexp we can use for locations, but the second one not (^~): https://www.digitalocean.com/community/tutorials/understand

Prevent Arbitary HTTP Host header in nginx

2020-02-27 Thread Kaushal Shriyan
Hi, Is there a way to prevent Arbitrary HTTP Host header in Nginx? Penetration test has reported accepting arbitrary host headers. Thanks in Advance and I look forward to hearing from you. More Information as below:- https://www.acunetix.com/blog/articles/automated-detection-of-host-header-attack

RE: problem with proxy pass

2020-02-27 Thread Reinis Rozitis
> From the hosts outside i've no connection problem, but from inside they are > unable to connect to the port. No firewall are enable on Nginx LB( Centos 7 > machine by the way) and Selinux is disabled. By "from inside" you mean other hosts in LAN or the same centos machine? If first then it's

R: problem with proxy pass

2020-02-27 Thread Stefano Serano
Hi all. I'm trying to use nginx as load balacer form my HIDS system (Wazuh). I've hosts that send logs from outside of my network and from inside throught port udp 1514. >From the hosts outside i've no connection problem, but from inside they are >unable to connect to the port. No firewa

Re: Deploying django, channels and websockets with nginx and daphne

2020-02-27 Thread Larry Martell
On Wed, Feb 26, 2020 at 6:39 PM Francis Daly wrote: > > On Wed, Feb 26, 2020 at 05:55:02PM -0500, Larry Martell wrote: > > Hi there, > > > upstream django { > > server unix:/run/daphne/devAppReporting.sock; > > } > > > > server { > > listen 8090; > > > location / { > >