Unable to Access JSON API about httpstatuses HOT 9 OPEN

@qw3rtman That was never an intentional feature, I didn't realise anyone was even doing that on the old site. I can definitely add this to the new site, can you outline how you were using it and what would be the ideal way for it to work? Do you need to get an entire class of code at once, or is one code at a time better?

from httpstatuses.

@qw3rtman short term (if this needs to be fixed immediately, rather in the next day or so) the old content is still available via some old commits in the repository, you could conceivably pull from that:

https://raw.githubusercontent.com/citricsquid/httpstatuses/6d5380e1effd6668ed26c4abc822fedda2082d58/codes/1.json
https://raw.githubusercontent.com/citricsquid/httpstatuses/6d5380e1effd6668ed26c4abc822fedda2082d58/codes/2.json
https://raw.githubusercontent.com/citricsquid/httpstatuses/6d5380e1effd6668ed26c4abc822fedda2082d58/codes/3.json
https://raw.githubusercontent.com/citricsquid/httpstatuses/6d5380e1effd6668ed26c4abc822fedda2082d58/codes/4.json
https://raw.githubusercontent.com/citricsquid/httpstatuses/6d5380e1effd6668ed26c4abc822fedda2082d58/codes/5.json

Sorry the issues caused! I should have been more careful with understanding the way the site was being used. Depended on google analytics for an overview, completely missing that I wouldn't be able to see non-web requests that way.

from httpstatuses.

No worries, completely understandable!

I was originally getting an entire class of codes at once, since that's how the "API" (:wink:) worked back when I wrote hsc and hsc-cli; however, I'm open to whatever seems practical to you. Personally, it makes more sense to be able get one code at a time. For some applications, it may be useful to get entire classes codes as well. Something like below might be a happy medium:

GET api.httpstatuses.com/v1/codes/4

{
    "class": {
        title: "Client Error",
    },
    "codes": {
        400,
        401,
        402,
        403,
        404,
        405,
        406,
        407,
        408,
        409,
        410,
        411,
        412,
        413,
        414,
        415,
        416,
        417,
        418,
        421,
        422,
        423,
        424,
        426,
        428,
        429,
        431,
        451,
        499
    }
}

GET api.httpstatuses.com/v1/code/404

"404":{
    "code":"404",
    "title":"Not Found",
    "summary":"requested resource could not be found",
    "descriptions":{
        "wikipedia":{
            "body":"The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.",
            "link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#404"
        },
        "ietf":{
            "body":"The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.",
            "link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
        }
    },
    "references":{
        "rails":{
            "title":"Rails HTTP Status Symbol",
            "value":":not_found"
        }
    }
}

Sorry for the late response!

from httpstatuses.

@qw3rtman Thank you for your thoughts! I'll get the API up ASAP and let you know once it's ready for use.

from httpstatuses.

Did this ever eventuate?

from httpstatuses.

@rickysullivan Hi! I sold the site about 2 years ago and at the time there wasn't an API yet. After the sale this repository was transferred to the acquirer (Ryan of webpagefx.com) and this repository became a read only archive -- as far as I know. For any site development you'd probably need to reach out to webpagefx directly to determine the current status of the project, as far as I know development has been frozen since the acquisition so I don't think it's likely there's any active development on any features (like an API) but I can't speak for them.

from httpstatuses.

Ah. Thanks for letting me know.

from httpstatuses.

It'd be great if a pinned issue and note on the README mentioned that this project was effectively inactive.

from httpstatuses.

The is already a new active fork that continues the work. The new page is https://httpstatuses.io.

Additionally I just created a fork ot that fork that provides an additional JSON endpoint, f.e. to get the JSON info of the 200 OK:

GET https://httpstatuscodes.io/200.json

The web page is available at https://httpstatuscodes.io/200

from httpstatuses.