overview for Ooops

No. I do however remember questioning people's sanity when they talked about stupid and incompetent politicians when it was very obvious that they were corrupt but knew very well what they were doing.

Decades later not much has changed. The malicious working against voters has become even more obvious and people still pretend that those corrupt shitbags are mostly just dumb and don't know any better.

Anthropic IPO could raise $100 billion at $2 trillion valuation by Ooops in c/technology@beehaw.org

[-] Ooops@feddit.org 11 points 1 day ago

But they bring many, many more people onboard to help pumping the bubble and later pressure the government to save them once that absolute insanity finally bursts.

EU Council text lists 6 cookie purposes that would need no consent by Ooops in c/europe@feddit.org

[-] Ooops@feddit.org 8 points 1 day ago* (last edited 1 day ago)

At the moment you have to click on the cookie banner on every single website. It’s just pain in the ass for any user.

You don't have to click those banners because they are neccessary but because the sites intentionally show them to you again and again and again as propaganda against data protection.

Edit: case in point... when you open lemmy.world to type your comment your browser gets checked by Cloudflare and then a cookie gets placed to mark you as having passed the check. They could theoretically also use this cookie to analyse user behavior by logging how often and when you visit the site, how many topics you open up to read per visit and so on... All without needing to show you a cookie banner as they are simply not using private data that can be used to identify you.

EU Council text lists 6 cookie purposes that would need no consent by Ooops in c/europe@feddit.org

[-] Ooops@feddit.org 6 points 1 day ago

If your "analytics" did not include collecting personal data that can used to identify them, you never needed that banner in the first place.

this is the start of everything falling apart, i can feel it by Ooops in c/programmer_humor@programming.dev

[-] Ooops@feddit.org 9 points 1 day ago

Sure. You can totally avoid them. Just by using very basic sentences. The same is true for a lot of puctuation.

But that doesn't make your sentences planned better but is simply a sign of limiting yourself by avoiding any complexity.

Imagine saying shit out loud. by Ooops in c/noncredibledefense@sh.itjust.works

[-] Ooops@feddit.org 21 points 2 days ago

If you make a sumo analogy you should perhaps know enough about sumo to understand that being the light-weight sumo wrestler in a sport without weight divisions is not the flex you think it is...

Denmark has abandoned plans to ditch Microsoft Office after technical problems by Ooops in c/europe@feddit.org

[-] Ooops@feddit.org 27 points 2 days ago

The flow of bribe money and favors not continuing might be a problem for some, but I would not categorise it as a "technical" one.

34

the boring one running on my ancient toaster for many years [i3, transparent xfce-panel over conky as bottom bar] (lemmy.nz)

submitted 4 months ago by Ooops@feddit.org to c/unixporn@lemmy.world

1 comments fedilink

25

Need some ELI5 on proxy_pass in Nginx, in particular regarding having Anubis in the chain (feddit.org)

submitted 6 months ago* (last edited 6 months ago) by Ooops@feddit.org to c/selfhosted@lemmy.world

11 comments fedilink

As this will -thanks to me being quite clueless- be a very open question I will start with the setup:

One nginx server on an old Raspi getting ports 80 and 443 routed from the access point and serving several pages as well as some reverse proxies for other sevices.

So a (very simplified) nginx server-block that looks like this:

# serve stuff internally (without a hostname) via http
server {
	listen 80 default_server;
	http2 on;
	server_name _; 
	location / {
		proxy_pass http://localhost:5555/;
                \# that's where all actual stuff is located
	}
}
# reroute http traffic with hostname to https
server {
	listen 80;
	http2 on;
	server_name server_a.bla;
	location / {
		return 301 https://$host$request_uri;
	}
}
server {
	listen 443 ssl default_server;
	http2 on;
	server_name server_a.bla;
   	ssl_certificate     A_fullchain.pem;
    	ssl_certificate_key A_privkey.pem;
	location / {
		proxy_pass http://localhost:5555/;
	}
}
#actual content here...
server {
	listen 5555;
	http2 on;
    	root /srv/http;
	location / {
        	index index.html;
   	} 
    	location = /page1 {
		return 301 page1.html;
	}
    	location = /page2 {
		return 301 page2.html;
	}
        #reverse proxy for an example webdav server 
	location /dav/ {
		proxy_pass        http://localhost:6666/;
	}
}

Which works well.

And intuitively it looked like putting Anubis into the chain should be simple. Just point the proxy_pass (and the required headers) in the "port 443"-section to Anubis and set it to pass along to localhost:5555 again.

Which really worked just as expected... but only for server_a.bla, server_a.bla/page1 or server_a.bla/page2.

server_a.bla/dav just hangs and hangs, to then time out, seemingly trying to open server_a.bla:6666/dav.

So long story short...

How does proxy_pass actually work that the first setup works, yet the second breaks? How does a call for localhost:6666 (already behind earlier proxy passes in both cases) somehow end up querying the hostname instead?

And what do I need to configure -or what information/header do I need to pass on- to keep the internal communication intact?