greptilian logo

IRC log for #rest, 2014-10-14

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:33 lemur joined #rest
02:48 mgomezch joined #rest
02:48 locks_ joined #rest
02:49 blindscreen_ joined #rest
02:49 gluegadget_ joined #rest
02:50 blongden_ joined #rest
02:50 trygvis_ joined #rest
03:23 jgornick joined #rest
05:21 MasterPiece joined #rest
05:46 `0660 joined #rest
06:17 proteusguy joined #rest
06:36 rosstuck joined #rest
06:43 _ollie joined #rest
09:28 proteusguy joined #rest
11:21 Left_Turn joined #rest
11:43 rue_XIV joined #rest
11:48 mezod joined #rest
12:33 t_dot_zilla joined #rest
13:00 foist joined #rest
13:15 shrink0r joined #rest
13:27 interop_madness joined #rest
14:20 saml joined #rest
15:07 mezod joined #rest
15:11 jgornick Hey guys, in a multipart/form-data message, instead of providing a file upload part or a key/value part, could I include a part that contains a Content-Location header which specifies where to download the content from?
15:50 foist joined #rest
16:06 trygvis jgornick: you can do what you want to, but it doesn't sound like someone else could put into a media type
16:07 trygvis as an alternative you can include multiple Link headers
16:07 trygvis wait, you want to POST a Content-Location to the server and have the server download it from a third party?
16:08 jgornick trygvis: If I'm reading the spec right, in a body part of a multipart message, you can include any header fields you'd like, particularly Content-* header fields are mentioned: http://tools.ietf.org/html/rfc1521#section-7.2 - 2nd paragraph in that section.
16:09 trygvis sure, you can include whatever you want
16:10 trygvis but the message type you're sending (multipart/form-data) doesn't specify how to process those headers
16:24 ph88 joined #rest
16:38 foist joined #rest
16:50 jgornick trygvis: If I follow the RFC trail: 2388 derives from 1867 which derives from 1521. RFC 1521 contains the how, right? Or is this not how RFCs work?
16:51 jgornick In RFC 1867 it says: "The media-type multipart/form-data follows the rules of all multipart MIME data streams as outlined in RFC 1521"
17:12 digitalsanctum joined #rest
17:43 trygvis I'm not saying you can't send it
17:43 trygvis you can send any header you want really
17:58 _ollie1 joined #rest
18:02 jcromartie joined #rest
18:22 _ollie joined #rest
19:01 _ollie joined #rest
19:24 jcromartie joined #rest
19:25 tr3online joined #rest
19:31 ordnungswidrig joined #rest
19:35 danfinch joined #rest
19:51 DracoBlue joined #rest
20:08 Mxyzpltk joined #rest
20:30 begriffs joined #rest
20:55 mezod joined #rest
20:55 mezod joined #rest
20:57 mezod joined #rest
21:16 talios joined #rest
21:52 shrink0r joined #rest
22:08 pdurbin "XPath, but for JSON" http://jmespath.org
22:15 _ollie1 joined #rest
22:21 talios that. looks. scary.
22:21 talios neat tho!
22:21 talios no Java version :( poop
22:22 pdurbin talios: you could file an issue: https://github.com/jmespath :)
22:22 talios That would be too constructive tho :
22:29 pdurbin apparently it's part of some AWS SDK: http://irclog.perlgeek.de/crimsonfu/2014-10-14#i_9509478
23:21 danfinch joined #rest

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

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