[–] 4 points 1 hour ago (2 children)

Danke dafür, nicht irrtümlicherweise wie so viele Menschen von Steingärten zu reden. Die sind im Gegensatz nämlich schön und sinnvoll.

  • source
  • [–] 6 points 12 hours ago

    especially if you use the AUR

    Which you do by default even without knowing it as Manjaro comes with an AUR helper pre-installed and also skips all the "this is user generated content; use at own risk"-warnings an Arch user would find in the wiki when trying to install something from the AUR.

  • source
  • parent
  • context
  • [–] 1 point 17 hours ago

    Ich glaube, da zittert jemand wegen der nächsten Landtagswahl.

    Klar, das wird total helfen, damit Idioten, die die AfD wählen, jetzt wegen ein paar Cent pro Liter ihre Entscheidung überdenken, oder damit Menschen, die sich "Verpulvern von Steuergeldern and die Fossilindustrie, Episode 492384" anschauen, plötzlich zu der Erkenntnis kommen, dass der korrupte Haufen doch wählbar ist.

    Oh, Moment... wohl eher nicht.

  • source
  • parent
  • context
  • [–] 2 points 18 hours ago (1 child)

    Ich hatte jetzt eher an sowas hier gedeacht:

    Also ein Becken, wo ich alleine schon nur über die Leitern rein und raus komme, wenn ich nicht gerade das Sprungvermögen eines Delphins habe...

  • source
  • parent
  • context
  • [–] 21 points 1 day ago*

    And who's going to block all the freely available DNS servers, proxies and also TOR? 😆

    That's just another piece of bullshit legislature to enact censorship measures in the name of some seemingly legit reason. You will never actually get rid of piracy sites with local ISP and DNS blocks. But the moment there is a procedure to easily make them happen, they can indeed be used to block the not tech-affine majority of people from news and information they should not see.

  • source
  • [–] 34 points 1 day ago

    Eine für Anfang 2027 geplante Live-Tour des Rundfunk-Tanzorchester Ehrenfeld wird abgesagt

    Klar, das kilngt total nach, war absolut so geplant und man ist in konstruktiven Gesprächen...

  • source
  • [–] 4 points 1 day ago* (last edited 1 day ago)

    Manchmal ja, manchmal nein. Einige machen die klare Unterscheidung, andere nicht.

    Im Bereich des Katastropehnschutzes sieht die Vereinheitlichung der Terminologie z.B. folgendes vor:

    "Bergung ... umfasst Maßnahmen zur Befreiung von Menschen oder Tieren, die durch äußere Einwirkungen in ihrer Bewegungsfreiheit eingeschränkt sind."


    Wörterbuch des Zivil- und Katastrophenschutzes

    Da würde wohl so mancher Ertrinkende drunter fallen.

  • source
  • parent
  • context
  • [–] 6 points 1 day ago (7 children)

    Punkt 3 ist in so ziemlich jedem Schwimmbad, in dem ich zu Schulzeiten war faktisch unmöglich... Da hätte niemand eine zu rettende Person ohne Hilfe Dritter die Leitern (als einzige Zugänge) hochbekommen.

  • source
  • parent
  • context
  • [–] 4 points 1 day ago*

    Do these fools even listen to themselves?

    They don't care if they are contradicting themselves as the same people paying them to tell such bullshit will also pay the media to push narratives 24/7 creating the sufficient amounts of cognitive dissonance.

  • source
  • parent
  • context
  •  

    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?

    view more: next ›