| Time |
S |
Nick |
Message |
| 01:13 |
|
|
tbsf joined #rest |
| 01:17 |
|
|
fuzzyhorns joined #rest |
| 01:51 |
|
|
tbsf joined #rest |
| 03:36 |
|
|
tbsf joined #rest |
| 04:07 |
|
|
tbsf joined #rest |
| 07:41 |
|
|
Seminarian joined #rest |
| 07:41 |
|
|
Haudegen joined #rest |
| 08:08 |
|
|
tbsf joined #rest |
| 08:48 |
|
|
d4rklit3 joined #rest |
| 08:56 |
|
|
interop_madness joined #rest |
| 10:35 |
|
|
Haudegen joined #rest |
| 11:45 |
|
|
Haudegen joined #rest |
| 12:01 |
|
|
Haudegen joined #rest |
| 12:08 |
|
|
tbsf joined #rest |
| 12:14 |
|
|
zama joined #rest |
| 12:39 |
|
|
bigbluehat joined #rest |
| 14:17 |
|
|
wsiqueir joined #rest |
| 14:44 |
|
|
tellnes joined #rest |
| 15:01 |
|
|
philbot joined #rest |
| 15:01 |
|
|
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 |
| 15:03 |
|
|
pdurbin joined #rest |
| 15:37 |
|
|
tbsf joined #rest |
| 15:55 |
|
bigbluehat |
anyone here know how to send an `OPTIONS *` request via curl (or similar)? |
| 15:56 |
|
bigbluehat |
hrm... apparently curl's out http://stackoverflow.com/a/36933053/507169 |
| 16:05 |
|
|
zama joined #rest |
| 16:19 |
|
|
zama joined #rest |
| 16:33 |
|
mamund_ |
srsly? |
| 16:33 |
|
mamund_ |
curl can't send OPTIONS? |
| 16:34 |
|
asdf |
"OPTIONS *", not OPTIONS in general |
| 16:34 |
|
|
tbsf joined #rest |
| 16:35 |
|
asdf |
i was wondering why would you ever want that and the rfc answers that too |
| 16:35 |
|
asdf |
Since a server's communication options |
| 16:35 |
|
asdf |
typically depend on the resource, the "*" request is only useful as a |
| 16:35 |
|
asdf |
"ping" or "no-op" type of method; |
| 16:36 |
|
|
tbsf joined #rest |
| 16:36 |
|
mamund_ |
well, i'd like to see the RFC details on how to _send_ that request. |
| 16:37 |
|
mamund_ |
typcially, you pass the URL, right? |
| 16:37 |
|
mamund_ |
but here you are passing a '*'? |
| 16:37 |
|
asdf |
ayup. `OPTIONS * HTTP/1.1` |
| 16:37 |
|
mamund_ |
i guess you really want to pass OPTIONS * to http://amundsen.com |
| 16:38 |
|
mamund_ |
so you need to pass the HOST header, i guess |
| 16:38 |
|
asdf |
Host is required by http1.1 anyway, isnt it? |
| 16:39 |
|
mamund_ |
right, so i am thinking that might be something you need to do for CURL |
| 16:39 |
|
mamund_ |
-H HOST? |
| 16:39 |
|
mamund_ |
or something? |
| 16:39 |
|
asdf |
oh right, curl, sorry |
| 16:39 |
|
mamund_ |
this is really a curl challenge<G> |
| 16:40 |
|
mamund_ |
hmmm.... |
| 17:35 |
|
whartung |
Hey mamund_ how u b? |
| 18:23 |
|
|
Seminarian joined #rest |
| 18:42 |
|
bigbluehat |
mamund_ and asdf issue filed fwiw https://github.com/curl/curl/issues/1280 |
| 18:44 |
|
bigbluehat |
OPTIONS * has been around since the beginning fwiw (RFC2068 FTW!) https://tools.ietf.org/html/rfc2068#section-5.1.2 |
| 18:44 |
|
bigbluehat |
still there in rfc7230 also https://tools.ietf.org/html/rfc7230#section-5.3.4 |
| 18:45 |
|
bigbluehat |
sadly this RFC (perhaps relatedly) hasn't gotten wide adoption https://tools.ietf.org/html/rfc2817#section-3.2 |
| 18:46 |
|
bigbluehat |
might have fixed the whole `http` !== `https` mess |
| 18:46 |
|
|
wsieroci joined #rest |
| 18:51 |
|
asdf |
eh, it's up to the client to send it, though - so it's mostly the same as HSTS? |
| 18:51 |
|
asdf |
i guess unless clients would always blindly send it first |
| 18:52 |
|
asdf |
(then they'd need to trust the response received over http :) ) |
| 18:52 |
|
whartung |
well technically the request doesnt; need a host, the connection does however. |
| 19:09 |
|
|
Seminarian joined #rest |
| 20:11 |
|
|
interop_home joined #rest |
| 21:23 |
|
|
d4rklit3 joined #rest |
| 22:18 |
|
|
tbsf joined #rest |
| 22:19 |
|
|
tbsf joined #rest |
| 23:57 |
|
|
fuzzyhorns joined #rest |
| 23:57 |
|
|
foist_ joined #rest |
