Tag Info

Hot answers tagged

3

The console JS was doing fuzzy matching on ?site; but that's not really correct, as you demonstrated. With the latest deploy it does an exact match if possible.


3

This was fixed in the latest deploy.


3

We moved from nginx to HAProxy for our SSL provider this weekend as part of a larger rollout. In the move, we shifted our header checks to the now de-facto standard SSL protocol header. While I thought I fixed all the apps relying on the old header and standardized everything internally, stackexchange.com was left out and thought your auth requests weren't ...


2

This was fixed in the latest deploy. Sorry about the wait, a fix was actually staged a few days ago but deploying it was delayed by our yearly company get together.


2

This was fixed in the latest deploy. Root cause: I had let a copy of our JSON serializer (currently ServiceStack.Text) get out of date.


2

The flag I think you're referring to was a recommend closure flag, which results in the post going to the Close Votes queue – not the actual flag queue, which currently has no backlog. Our flag response time is pretty good at the moment, sitting at a little under two and a half hours. It had recently been even better than that recently, but I've ...


2

This was fixed in the latest deploy. The bug was basically selecting the wrong date to display (in this case, an associated post), and the right date for filtering and what not. Since not all badges are associated with a post, not all displayed dates were set and when they were set they were off by some (basically random) amount.


2

This was fixed in the latest deploy.


1

The inname parameter restricts the results of a name search to only those that contain the specified substring. The following methods support it: /badges /badges/name /badges/tags /users /tags /tags/required /tags/moderator-only filtering on badge, user, or tag names, as applicable.


1

There was some monkeying around on the backend with URI generation, it's settled down now and this issue was resolved.



Only top voted, non community-wiki answers of a minimum length are eligible