greptilian logo

IRC log for #rest, 2016-11-23

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
00:12 fuzzyhorns joined #rest
02:27 philbot joined #rest
02:27 Topic for #rest is now #rest REpresentational State Transfer | logs: http://irclog.greptilian.com/rest/today |  http://tech.groups.yahoo.com/group/rest-discuss | http://code.google.com/p/implementing-rest/ | http://en.wikipedia.org/wiki/Representational_State_Transfer
02:28 pdurbin joined #rest
02:44 tilerendering_ joined #rest
05:22 sp1rs joined #rest
06:17 sp1rs joined #rest
06:39 talios joined #rest
06:53 sp1rs joined #rest
08:10 sp1rs joined #rest
08:39 sp1rs joined #rest
13:19 Tomatosoup- joined #rest
14:26 ShekharReddy joined #rest
14:59 talios joined #rest
15:10 wsieroci joined #rest
16:01 kke joined #rest
16:03 kke left #rest
16:29 cuqa joined #rest
16:31 cuqa hello, I am currently in the early stage of creating a rest api, now I tried to test the http response code with "curl -I", so a HEAD request..
16:32 cuqa now I am confused how to treat HEAD requests .. return some kind of error, that this verb is not supported or do reply to it?
16:32 cuqa what is a good practice?
16:33 asdf cuqa, sure, send the same response as you would for GET, but without a response body
16:33 pdurbin cuqa: you should support "curl -I"
16:34 asdf cuqa, btw, the 'http semantics' rfc might be enlightening for these kinds of questions (rfc 7231)
16:35 cuqa ok, thanks a lot
17:54 talios joined #rest
18:00 Tomatosoup- joined #rest
20:03 Tomatosoup- joined #rest
20:46 anth0ny joined #rest
21:31 fuzzyhorns joined #rest
22:07 Haudegen joined #rest

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

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