LornaJane

Quicksearch

Comments

Sun, 05.07.2009 10:29
Alexandr: I like to use both – return a status code so anything that cares can see it, then make the body of the thing a sensible error message. Caius: You are providing us good and sensible advice, thanks for dropping by :) lifeforms: I have no idea how the codes get decided upon but I [...]
Sun, 05.07.2009 10:26
Jaime: Yay! Will be great to catch up with you in person, seems like ages :)
Jaime Hemmett about PHPNW: Site, Tickets and CfP
Sat, 04.07.2009 11:47
I’m planning to come. Friend that just moved to Manchester says he has a spare room too!! WIN. Actually This probably means I can buy flights soon :D.
Sat, 04.07.2009 00:23
I wish there were some more 4xx error codes. They are so arcane and not really fit with today’s use of HTTP as an application protocol. I would love for some extra codes like missing request parameter, parameter validation failed, etc…
Caius Durling about Status Codes for Web Services
Fri, 03.07.2009 21:14
Using a HTTP Error code doesn’t stop you serving up a custom error page. In fact thats the best way to do it. People who visit with a web browser will be none the wiser, but anyone that needs to programatically find out what the server responded with can. And if you’re serving up an API err [...]
Fri, 03.07.2009 19:31
I don’t use errors codes at all. Custom error pages with description what is happened and recommendation what user need to do – it is my way. Keep in mind not all users can understood error by number and less of them will know what to do.
Fri, 03.07.2009 11:38
shangxiao: my manager is geeky enough that he’d know perfectly well what I was talking about if I used a 4xx code at him :)
Fri, 03.07.2009 06:21
I gather most js libraries will now provide an error handler for 4xx and 5xx, which is quite handy to know whether to display an error dialog. I also use 4xx for when client errors eg when a db constraint fails, I respond with a 4xx and put the error message in the body of the response. For [...]
Thu, 02.07.2009 12:22
Gaetano: I quite like having the version in the URL but that depends a lot on what kind of service you designed as to what makes most sense. I like major.minor as a naming scheme but it is probably overkill as really APIs shouldn’t be changing a lot. Chris: Whether you support multiple ver [...]