Maybe sort by “date” instead of date & site?
Sounds like someone could use some more shut the fuck up Friday in their life 😘
That’s an interesting idea. Do you write a blog or something where I can learn more?
Armchair General here. When they moved their aircraft further back, Russia greatly reduced their range and ordnance options while increasing the time Ukraine had to prepare for the strikes. Similarly, Russia splitting up their stockpiles to reduce strike effectiveness will have a significant impact on Russia’s already-strained logistics network. That’s the same reason why a relatively low volume of ATACMS has had such a substantial impact on their ability to wage war.
Can you clarify what you mean by that? It sounds strangely gatekeepy to me, but maybe I’m misunderstanding
Where is your VPS located, and which Wire Guard server are you connecting to?
In your HAProxy config (like in this example), it’s checked from top to bottom. So your top-most frontend case should be the one that checks for the special keyword case. Then, if it doesn’t match the keyword, HAProxy will continue going down the list until it finds a frontend that does match. So your second frontend should match for everything, because if it doesn’t find a match, HAProxy shows an error
Cool, I think that first link will work for you. Then you can just ‘redirect’ for the no-keyword case: https://www.haproxy.com/documentation/haproxy-configuration-tutorials/http-redirects/
Remember, SSL/HTTPS does encrypt the URL path, so if the final website requires HTTPS, your proxy will need to have its certificate trusted by your clients
Maybe have two cases:
For the (matched keyword) case, something like this: https://serverfault.com/questions/729232/reg-exp-for-url-in-haproxy
For the (random routing) case, something like: https://www.haproxy.com/blog/haproxy-configuration-basics-load-balance-your-servers
I am a little confused on your question, though. It sounds like you maybe want 3 cases? Can you try wording it differently?
Generally unique request IDs have to be generated by the client that sends the request. If the client doesn’t generate an ID, you’re probably out of luck. That said, do you have information about the client you’re expecting to call your Squid cache? One unofficial, but common place for clients to put a request ID is in the header “X-Request-ID”
I’m confused, yet inspired
I was waiting so long for this release that I gave up a couple of months ago and built from source 😂
Being “used to” something and being “ashamed” are mutually exclusive, so I’m having a difficult time understanding your overall point or position
deleted by creator
I think it’s reasonable that you chose that title based on the email header, and I also think it’s very irresponsible of haveibeenpwned to send out an email with that subject line. They absolutely should know better.
“Breached” implies that sensitive data, like payment details, private communication, or physical addresses, were leaked. Instead, this is just semi-public stuff like email/username/name. Maybe a better title would be “15M Trello users have been identified (name/email)”
Awesome! Thanks for the detailed update, and I’m glad it worked well for you!