

Wow, no ambiguity or anything. Jesus Fucking Christ


Wow, no ambiguity or anything. Jesus Fucking Christ


idk if this is a programming specific question. It feels more like “perfectionism” or a low-level OCD. For the programming piece, using some sort of task tracking system might be helpful. For example, after a task has been completed (aka a solution was found), move on to the next predefined task.
Another vaguely related term: premature optimization
I’m literally a software dev working for a top company and I can barely use git on the CLI. I do all of my version control operations using a GUI, so there’s no sense in gatekeeping any of that. This is true of both my work projects and personal ones. It’s cool if you prefer the CLI, but it is absolutely not a required skill in order to have a successful and meaningful career.


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”
Tangential thought: maybe the two are related? Like, on days where you’re super busy, you’re more likely to get a bit dehydrated from the busyness (lol, root of business?), and ALSO more likely to miss steps in the evening routine, like bringing the water bottle to bed, for the same reason.
My friend, you think this likely because your family exhibits these traits (genetics) as do your friends(attracted to like groups). You’re using two ADHD meme traits, like thinking everyone feels this way and using extra parentheses (for bonus content). I bet you’ve also been told that you’re not living up to your potential (and that’s true!).
If you want something objective, have a coffee or two at 6pm and see if you’re still able to fall asleep that night. The neuro typical folks would be unable to quiet down their brain.
Hi, dropping in to say that everyone who relates to this has undiagnosed ADHD. Getting diagnosed at 29 was life changing for me
Sometimes I fork to make changes locally, but they’re either me-specific or hacky garbage I don’t want to publish. Because of that, I normally don’t commit those changes, and definitely don’t push to GitHub or make a PR.