All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Nginx proxy_pass won't work due to a script in a different location
Hi,
I'm currently trying to use a nginx reverse proxy to hide an RMTP portal so it doesn't get ddosd however I've ran into an issue as the page I'm passing to calls a script from the top level domain and not that sub domain where the portal is located so it thinks the file should be on the reverse proxy server.
Portal location: domain.net/test/index.html
Script location: domain.net/Auth.js
Reverse proxy (seperate server): domain2.net
When I go to the page via the reverse proxy it all works (all the js scripts in the location render fine)except I get a 404 as it thinks the script should be at domain2.net/Auth.js when it's on the server I'm passing to.
I don't have access to the portal server either otherwise could of just moved the auth file into the location.
Any help would be appreciated 
Cheers
Comments
Telnet/netcat to HTTP and do an HTTP/1.1 request with the Host header and see if it works. If so, you've found what you need to set/implement.
Not that clued up enough to do that lol
Sigh Use proxy_set_header.
Have you tried to use ipv6 to stop ddos attacks?
What the hell is setting up Ipv6 has with mitigating ddos?
I don't think Winnuke supports IPV6.
I'd like to do it the way I posted :-)
Whats your proxy config?
Are you proxying every request or only a specific file type?
From my research it seems that the Raspberry pi website hosts use ipv6 to stop or lessen ddos attacks. The company has a video on YouTube that explains this. I tried it but I could not get hit hub to work.
Oh, not sure what Winnuke is. God bless you.
Oh, he has. He has. Wanna peek?
No thanks, but WSS is correct many of scripts that are for ddos are ipv4 only. So many who just use the programs or scripts may not know how to deploy an attack on ipv6.