Skip to main content
Stack Apps

Return to Question

replaced http://stackapps.com/ with https://stackapps.com/
Source Link
Community Bot
Community Bot
  • 1

Right now questions tagged soapi.csquestions tagged soapi.cs returns a HTTP status code 404 (for various HTTP clients) while questions tagged soapi.jsquestions tagged soapi.js does not.

Interestingly though, soapi.cs seems to work just fine in other places, e.g. Newest soapi.cs questionsNewest soapi.cs questions returns the desired result, and so does Stats on soapi.csStats on soapi.cs. That is, as soon as (sort) parameters are included the route seems to work as expected, but not without?

What's the magic difference here?

Right now questions tagged soapi.cs returns a HTTP status code 404 (for various HTTP clients) while questions tagged soapi.js does not.

Interestingly though, soapi.cs seems to work just fine in other places, e.g. Newest soapi.cs questions returns the desired result, and so does Stats on soapi.cs. That is, as soon as (sort) parameters are included the route seems to work as expected, but not without?

What's the magic difference here?

Right now questions tagged soapi.cs returns a HTTP status code 404 (for various HTTP clients) while questions tagged soapi.js does not.

Interestingly though, soapi.cs seems to work just fine in other places, e.g. Newest soapi.cs questions returns the desired result, and so does Stats on soapi.cs. That is, as soon as (sort) parameters are included the route seems to work as expected, but not without?

What's the magic difference here?

Replaced 'Info' with the more isntructive 'Newest' route and added speculation about parameters.
Source Link
Steffen Opel
Steffen Opel
  • 1.4k
  • 8
  • 14

Right now questions tagged soapi.cs returns a HTTP status code 404 (for various HTTP clients) while questions tagged soapi.js does not.

Interestingly though, soapi.cs seems to work just fine in other places, e.g. Info about soapi.csNewest soapi.cs questions returns the desired result, and so does Stats on soapi.cs. That is, as soon as (sort) parameters are included the route seems to work as expected, but not without?

What's the magic difference here?

Right now questions tagged soapi.cs returns a HTTP status code 404 (for various HTTP clients) while questions tagged soapi.js does not.

Interestingly though, soapi.cs seems to work just fine in other places, e.g. Info about soapi.cs returns the desired result, and so does Stats on soapi.cs.

What's the magic difference here?

Right now questions tagged soapi.cs returns a HTTP status code 404 (for various HTTP clients) while questions tagged soapi.js does not.

Interestingly though, soapi.cs seems to work just fine in other places, e.g. Newest soapi.cs questions returns the desired result, and so does Stats on soapi.cs. That is, as soon as (sort) parameters are included the route seems to work as expected, but not without?

What's the magic difference here?

Source Link
Steffen Opel
Steffen Opel
  • 1.4k
  • 8
  • 14

What's the difference between tags soapi.cs and soapi.js to get a bug triggered by the former?

Right now questions tagged soapi.cs returns a HTTP status code 404 (for various HTTP clients) while questions tagged soapi.js does not.

Interestingly though, soapi.cs seems to work just fine in other places, e.g. Info about soapi.cs returns the desired result, and so does Stats on soapi.cs.

What's the magic difference here?