In case you haven't considered this, some helpful advice.
To keep them from the lemmy.world door after the CDN installation
Change the public IP addresses
rotate your certificates
block all traffic appart from the CDN and only allow a limited known good IP addresses (like yours and your support team).
These steps will make your server harder to find, hopefully they move on.
Depending on your wifi/router you could add a static DNS record for your domain while on the hi home network. The cached DNS will only matter while connected to the home wifi network. While on 5g you'll pick up the public DNS record. If it does some how cache the local DNS while public then shorten the ttl in the local DNS record
These don't sound like a scalable cure
High rise residential building? /s
Monkey's wedding.
In case you haven't considered this, some helpful advice. To keep them from the lemmy.world door after the CDN installation
Never forget, in nineteen ninety eight when the undertaker threw mankind off hell in a cell and plummeted sixteen feet through an announcer's table.
I don't get this reference.
I'm not 100% on this but I think GET requests are logged by default.
POST requests, normally used for passwords, don't get logged by default.
BUT the Uri would get logged would get logged on both, so if the URI contained @username:Password then it's likely all there in the logs
Make sure it will stay relevant
Are you sure your not moving too fast?
huhThankyou for this, I'll do my bit 😃
Depending on your wifi/router you could add a static DNS record for your domain while on the hi home network. The cached DNS will only matter while connected to the home wifi network. While on 5g you'll pick up the public DNS record. If it does some how cache the local DNS while public then shorten the ttl in the local DNS record
This is the way, I've known it as feathering it out. This is the technique to blend the new and original.
She isn't stealing your shoe. She is stealing you bit by bit
It's my first day