Timeline for More complete "MutipartData" POSTs using URLFetch
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 2, 2017 at 3:38 | history | edited | ZachB | CC BY-SA 3.0 |
added 91 characters in body
|
| Oct 14, 2016 at 16:18 | comment | added | yode |
Wow,have you notice this post?Maybe the File can solve?
|
|
| Oct 14, 2016 at 3:26 | history | edited | ZachB | CC BY-SA 3.0 |
deleted 18 characters in body
|
| Oct 14, 2016 at 3:11 | history | edited | ZachB | CC BY-SA 3.0 |
added 209 characters in body
|
| Oct 12, 2016 at 19:01 | history | edited | ZachB | CC BY-SA 3.0 |
added 317 characters in body
|
| Oct 27, 2015 at 1:54 | comment | added | Christopher Haydock | Oops! I was confused about this point because I ran a "MultipartElements" syntax test that specified elements in mixed format: {"name","mimetype"} -> string and {"name","mimetype",byte-list}. This does not work. The same syntax must be used for all elements. | |
| Oct 25, 2015 at 18:36 | comment | added | ZachB |
@ChristopherHaydock yes, that's the bytes symbol in my example, if I understand what you're expecting. Thanks for the reference from the other answer :)
|
|
| Oct 24, 2015 at 21:52 | comment | added | Christopher Haydock | Does the MultipartElements option still accept a third byte list argument? | |
| Oct 24, 2015 at 21:52 | comment | added | Christopher Haydock | Thanks for the help answering another question! | |
| Oct 23, 2015 at 2:54 | history | answered | ZachB | CC BY-SA 3.0 |