greptilian logo

IRC log for #rest, 2017-02-16

https://trygvis.io/rest-wiki/

| Channels | #rest index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
01:15 tbsf joined #rest
01:27 tbsf joined #rest
01:46 tbsf joined #rest
01:48 tbsf_ joined #rest
02:11 tbsf joined #rest
02:32 fuzzyhorns joined #rest
04:31 tbsf joined #rest
05:03 tbsf joined #rest
06:03 tbsf joined #rest
06:58 tbsf joined #rest
07:31 timg__ joined #rest
08:12 wsieroci joined #rest
08:20 Haudegen joined #rest
09:02 interop_madness joined #rest
09:18 Haudegen joined #rest
11:25 sgfgdf joined #rest
11:44 ironChicken joined #rest
11:49 sgfgdf hello, guys! i have a question about handling REST API (JSON) errors. is there a common practice what the response should be? lets say you need to return 404 HTTP status, what the JSON response should be?
12:00 trygvis 404 is usually enough
12:01 trygvis but you can use vnd.error: https://github.com/blongden/vnd.error
12:49 timg__ joined #rest
12:59 sgfgdf trygvis: so this is like a recommended standard whcih you can implement or use a library to implement taht implements it in your choice of language?
13:31 trygvis something like that
13:39 Haudegen joined #rest
15:46 timg__ joined #rest
16:53 tbsf joined #rest
17:37 wsieroci joined #rest
18:30 tbsf joined #rest
18:59 wsiqueir joined #rest
19:46 tbsf joined #rest
19:58 tbsf joined #rest
20:20 timg__ joined #rest
20:23 timg__ joined #rest
20:26 wsieroci joined #rest
20:37 bluezone joined #rest
23:02 fuzzyhorns joined #rest
23:13 ReScO joined #rest

| Channels | #rest index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

https://trygvis.io/rest-wiki/