| Time |
S |
Nick |
Message |
| 00:04 |
|
|
huckleberry78 joined #rest |
| 00:27 |
|
|
gluegadget joined #rest |
| 00:27 |
|
|
zama joined #rest |
| 00:27 |
|
|
blongden joined #rest |
| 00:27 |
|
|
sulky joined #rest |
| 00:27 |
|
|
DrCode joined #rest |
| 00:27 |
|
|
shrink0r_ joined #rest |
| 00:27 |
|
|
Left_Turn joined #rest |
| 00:27 |
|
|
proteusguy joined #rest |
| 00:27 |
|
|
fumanchu joined #rest |
| 00:27 |
|
|
saml joined #rest |
| 00:27 |
|
|
jgornick joined #rest |
| 00:27 |
|
|
happyface_ joined #rest |
| 00:27 |
|
|
lemur joined #rest |
| 00:27 |
|
|
blahdeblah_ joined #rest |
| 00:27 |
|
|
ironChicken joined #rest |
| 00:27 |
|
|
mgomezch joined #rest |
| 00:27 |
|
|
danfinch joined #rest |
| 00:27 |
|
|
trygvis joined #rest |
| 00:27 |
|
|
rickharrison joined #rest |
| 00:27 |
|
|
ChrisAnn joined #rest |
| 00:27 |
|
|
`0660 joined #rest |
| 00:27 |
|
|
blindscreen joined #rest |
| 00:27 |
|
|
locks joined #rest |
| 00:27 |
|
|
heath joined #rest |
| 00:27 |
|
|
daxim joined #rest |
| 00:27 |
|
|
Jarda joined #rest |
| 00:27 |
|
|
riddle joined #rest |
| 00:27 |
|
|
ederign joined #rest |
| 00:27 |
|
|
pindonga joined #rest |
| 00:27 |
|
|
igitoor joined #rest |
| 00:27 |
|
|
pdurbin joined #rest |
| 00:27 |
|
|
alxbl joined #rest |
| 00:27 |
|
|
ekroon joined #rest |
| 00:27 |
|
|
bigbluehat joined #rest |
| 00:27 |
|
|
tmoore joined #rest |
| 00:27 |
|
|
Davey joined #rest |
| 00:27 |
|
|
dreamdust joined #rest |
| 00:27 |
|
|
ramsey joined #rest |
| 00:27 |
|
|
licyeus_ joined #rest |
| 00:27 |
|
|
HighBit joined #rest |
| 00:27 |
|
|
whartung joined #rest |
| 00:27 |
|
|
vlakarados joined #rest |
| 00:27 |
|
|
asm89 joined #rest |
| 00:27 |
|
|
gamache joined #rest |
| 00:27 |
|
|
asdf` joined #rest |
| 00:32 |
|
|
rue joined #rest |
| 00:40 |
|
|
shrink0r joined #rest |
| 00:58 |
|
|
shrink0r_ joined #rest |
| 01:18 |
|
|
shrink0r joined #rest |
| 02:35 |
|
|
shrink0r joined #rest |
| 05:17 |
|
|
proteusguy joined #rest |
| 06:02 |
|
|
shrink0r joined #rest |
| 06:57 |
|
|
rosstuck joined #rest |
| 07:51 |
|
|
shrink0r joined #rest |
| 08:18 |
|
|
fumanchu_ joined #rest |
| 08:55 |
|
|
Voyage joined #rest |
| 09:00 |
|
|
martinfilliau joined #rest |
| 09:23 |
|
|
sulky joined #rest |
| 09:33 |
|
|
mezod joined #rest |
| 09:36 |
|
|
lemur joined #rest |
| 09:39 |
|
|
shrink0r joined #rest |
| 09:46 |
|
|
Left_Turn joined #rest |
| 09:50 |
|
|
Andre-B joined #rest |
| 09:55 |
|
|
huckleberry78 joined #rest |
| 10:01 |
|
|
fumanchu joined #rest |
| 10:42 |
|
|
shrink0r joined #rest |
| 10:59 |
|
|
quimrstorres joined #rest |
| 11:07 |
|
|
marcoslamuria joined #rest |
| 11:12 |
|
quimrstorres |
hey there! i am struggling to find the right way to respond to an http request on my web api. i have a resource that, in some cases, it only returns part of the content. it is not a collection resource or anything. basically it is a resource that returns some metrics information, but it is possible that some of the metrics requested don't exist (the server does not support them). i'd like to return the value of the suppo |
| 11:12 |
|
quimrstorres |
rted metrics and some indication that some of them were not returned. |
| 11:13 |
|
trygvis |
so it does return all of the content |
| 11:13 |
|
trygvis |
or not? |
| 11:13 |
|
quimrstorres |
only if the server supports all of the metrics requested |
| 11:14 |
|
trygvis |
ok, but from a resource point of view it includes everything |
| 11:14 |
|
trygvis |
there is a difference between a partial response and a full response saying it doesn't support every part of the request |
| 11:15 |
|
quimrstorres |
yeah, you're right |
| 11:16 |
|
trygvis |
what was your question again? |
| 11:16 |
|
|
captain_furious_ joined #rest |
| 11:17 |
|
trygvis |
did you want a different response code if it didn't include all of the metrics? |
| 11:17 |
|
quimrstorres |
my question was how should i respond to the request. but as you said, from the resource point of view it's full response |
| 11:17 |
|
trygvis |
yep. so always 200 OK |
| 11:18 |
|
quimrstorres |
yep, thanks. would it make sense if the response indicated, in some way, that some of the metrics are not supported? |
| 11:19 |
|
quimrstorres |
with a warning header or something? |
| 11:20 |
|
tmoore |
I'd just make that part of the response format |
| 11:21 |
|
quimrstorres |
and by that you mean you'd send that info in the payload, right? |
| 11:24 |
|
tmoore |
yes |
| 11:28 |
|
trygvis |
yeah, that's definitely what you should do |
| 11:33 |
|
quimrstorres |
so, when should i use mechanisms like the warning header to indicate something to the client? |
| 11:34 |
|
trygvis |
probably never |
| 11:34 |
|
trygvis |
the application itself shouldn't care about the headers, it's not supposed to know its using http or pidgins |
| 11:49 |
|
|
quimrstorres joined #rest |
| 11:51 |
|
quimrstorres |
i think i don't totally agree with that last statement trygvis |
| 11:52 |
|
quimrstorres |
i think the purpose of using http as an applicational protocol is to use as much as its semantics as possible |
| 11:58 |
|
trygvis |
sort of, yes. but if you're inventing your own semantics and stuff that into http you more or less end up with your own protocol |
| 11:58 |
|
trygvis |
which I mean should be put into the payload instead |
| 11:58 |
|
trygvis |
sometimes stuff trickle down from the hypermedia into http, like the Link header |
| 12:13 |
|
|
zama joined #rest |
| 12:35 |
|
pdurbin |
I wonder if there's a concept of "empty but could be available" in http://transit-format.org |
| 13:05 |
|
|
quimrstorres joined #rest |
| 13:18 |
|
|
interop_madness joined #rest |
| 13:54 |
|
|
proteusguy joined #rest |
| 14:33 |
|
|
huckleberry78 joined #rest |
| 14:55 |
|
|
interop_madness joined #rest |
| 15:01 |
|
|
huckleberry78 joined #rest |
| 15:42 |
|
|
hucklebe_ joined #rest |
| 15:53 |
|
|
DrCode joined #rest |
| 15:57 |
|
|
huckleberry78 joined #rest |
| 16:08 |
|
|
huckleberry78 joined #rest |
| 16:14 |
|
|
ph88_ joined #rest |
| 16:20 |
|
|
huckleberry78 joined #rest |
| 16:26 |
|
|
shrink0r joined #rest |
| 16:29 |
|
|
huckleberry78 joined #rest |
| 16:29 |
|
|
shrink0r joined #rest |
| 16:40 |
|
|
huckleberry78 joined #rest |
| 17:06 |
|
|
huckleberry78 joined #rest |
| 17:09 |
|
|
huckleberry78 joined #rest |
| 18:02 |
|
saml |
do I include updated representation in the response of PUT? |
| 18:02 |
|
saml |
or just 204 ? |
| 18:05 |
|
Jarda |
I always include the updated response |
| 18:07 |
|
saml |
i did too |
| 18:07 |
|
saml |
this guy changed to 204 |
| 18:07 |
|
saml |
and made pull request |
| 18:07 |
|
saml |
trying to find a good reason to reject |
| 18:10 |
|
|
systmkor joined #rest |
| 18:11 |
|
trygvis |
perhaps this is what you should use: http://tools.ietf.org/html/rfc7240#section-4.2 |
| 18:12 |
|
Jarda |
I only use 204 for DELETE requests |
| 18:13 |
|
saml |
nice |
| 18:13 |
|
saml |
Prefer: |
| 18:18 |
|
saml |
curl -vso /dev/null -H 'Prefer: girl=pretty' www.google.com |
| 18:18 |
|
saml |
how come there are two Set-Cookie: header in the response? |
| 18:19 |
|
saml |
http://stackoverflow.com/questions/3241326/set-more-than-one-http-header-with-the-same-name looks like normal for Set-Cookie |
| 19:18 |
|
|
begriffs joined #rest |
| 19:21 |
|
|
shrink0r joined #rest |
| 20:53 |
|
|
quimrstorres joined #rest |
| 20:58 |
|
|
talios joined #rest |
| 21:33 |
|
|
sulky joined #rest |
| 21:41 |
|
|
marcoslamuria joined #rest |
| 23:17 |
|
|
systmkor1 joined #rest |
| 23:19 |
|
|
systmkor2 joined #rest |
| 23:54 |
|
|
begriffs joined #rest |
