• It already had the tag nginx which is the configuration language at hand.
  • The person that answered the question did a fine job and obviously knew what the question was about.

enter image description here

Unduplicating prox_pass in nginx location blocks

It's just annoying if you don't even do cursory googling to figure out if it's correct to lock it in the first place when it's that old and already answered with a correct tag.

And by cursory googling I mean this was literally the second result on Google for "nginx language".

| |
  • 1
    \$\begingroup\$ I did some searching myself, and perhaps I somehow missed that. If so, I apologize and I'll reverse these actions. \$\endgroup\$ – Jamal Dec 13 '16 at 3:30
  • 3
    \$\begingroup\$ @Jamal Retroactively locking questions from 2012 that has already been answered acceptably is still crazy even just because they are missing a tag. I have enough code to maintain already, why am I suddenly beholden to maintaining 4 year old stack overflow questions? \$\endgroup\$ – Kit Sunde Dec 13 '16 at 3:36
  • 3
    \$\begingroup\$ Please keep in mind that a closure is not the same as a lock. Old questions can still be dealt with for maintenance reasons, but in this case I was incorrect and I appreciate you bringing this to my attention. \$\endgroup\$ – Jamal Dec 13 '16 at 3:37
  • 1
    \$\begingroup\$ @Jamal Old questions should be dealt with by the moderator or the existing review tooling if the rules change where the Q&A is still considered to meet the quality standards. It's not cool to ask the user base to maintain things they posted years ago. \$\endgroup\$ – Kit Sunde Dec 13 '16 at 3:42

You must log in to answer this question.

Browse other questions tagged .