Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
A beautiful interface has a beautiful request and response structure just like that beautiful next door girl. A response code is like a state of the object the server has, how fuck can the client understand this. This is shit load of stuff man to parse.
So buddy fuckin shit that response code dump your parsing and ask the moron why 200 for everything. -
@eatPrayCode I would really like to just dump it. Unfortunately I'm creating a program for a client who wants a specific device with that cgi to be integrated. So no contact to the company who made it and even if there were, they would only release a patch and I find myself integrating both versions -.-
I'm writing a small blogging CMS in bash using CGI. I can't help but giggle every once in a while when I think...
Who the fuck uses http code 200 for a failure. Seriously have you ever heard something about a need to parse the shit you're returning...
Now I don't know whether it's me who's wrong, but man there are more than 80 different codes defined so there really should be something for you, don't you think?
And don't give me shit like "well the request worked so we return 200 it's only that the request wasn't correct". What for a fucking peace of something are you... Those codes are for that exact reason.
Anyways I'm going to parse the shit with string compare and afterwards kill myself out of shame. Whish me luck...
undefined
cgi
fuck errors
!parsableforthewin