Checks own servers...
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
Yeah, I'd like to see that...
Checks own servers...
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
Yeah, I'd like to see that...
No, it's still trying to get here with Deutsche Bahn.
Next, they’re bringing them democracy?
I don't know the Immich API, but I've seen several REST APIs that used the usual pattern of
GET /api/v1/user/<id> - read user
POST /api/v1/user/ - create user
...
but also allowed
GET /api/v1/user/<id> - read user
GET /api/v1/user/?action=create - create user
...
It's fine, the blockchain is now augmented with some AI and runs serverless in the cloud!
Well, in his dreams it did work out...
Boil 'em, mash 'em, stick 'em in a flu
SOURCE?
Don't worry. When the time is right (e.g. when there's some oil to be found) the USA will invade them and bring them democ.... oh....
I swear, I just need 4-5 more graphics cards to solve this!
Yeah, but now you’re talking about communicating with
web.archive.org
and notnonesense.reputable-bank.com
as in the original post. In this case you’re not even trying to hide the fact, that you aren’t affiliated withreputable-bank.com
and we're back to square one and you could also just usereputable-bank.com.some.malicious-phishing.website
to host your page.Btw: all modern browsers will warn you when you access a non-encrypted website - some immediately, some only when you try to enter data into a login form.