Dear kids, this is what happens when you let AI design your core infrastructure architecture...

RE: https://ipv6.social/@tschaefer/116071588412706294

Dear kids, this is what happens when you let AI design your core infrastructure architecture...

"For HTTP/HTTPS: The gateway automatically adds the X-Forwarded-For header. Configure your web server (for example: Nginx or Apache) to evaluate this header."

European sovereign clouds!!

EDIT: I don't even know how they want to add this header in HTTPS traffic... Maybe (i hope?) this whole article really is just hallucinated

@manawyrm

EDIT: I don’t even know how they want to add this header in HTTPS traffic… Maybe (i hope?) this whole article really is just hallucinated

Hopefully they’re using the Proxy Protocol.

But I have this horrible suspicion they’re not…

@erincandescent I don't think so:
- it would break existing applications
- it probably has the same/similar security implications
- they explicitly mention "X-Forwarded-For" by name

@manawyrm @amy oh die hatten sinnvollen IPv6 support, an den meisten stellen jedenfalls x)

@manawyrm @amy (dafür ein "Database as a Service" wo Kunden alles per Support ticket einkippen mussten; nix API)

@littlefox@gotosocial-dev.svc.0x0a.network @manawyrm@chaos.social @amy@mastodon.fibercut.org Für jeden SQL-Befehl? ​​

RE: https://ipv6.social/@tschaefer/116071588412706294

Dear kids, this is what happens when you let AI design your core infrastructure architecture...

"For HTTP/HTTPS: The gateway automatically adds the X-Forwarded-For header. Configure your web server (for example: Nginx or Apache) to evaluate this header."

European sovereign clouds!!

EDIT: I don't even know how they want to add this header in HTTPS traffic... Maybe (i hope?) this whole article really is just hallucinated

@manawyrm just give your cert to that gateway ^^

@CyReVolt @manawyrm aaaaaaaa

@manawyrm and i thought digitalocean making customers share /64s was bad