| Time |
S |
Nick |
Message |
| 00:03 |
|
|
lemur_ joined #rest |
| 02:42 |
|
|
PalyaPix joined #rest |
| 03:49 |
|
|
alxbl joined #rest |
| 04:02 |
|
|
asm89 joined #rest |
| 04:03 |
|
|
proteusguy joined #rest |
| 04:19 |
|
|
lemur joined #rest |
| 04:33 |
|
|
tr3online joined #rest |
| 04:41 |
|
|
tr3online joined #rest |
| 05:01 |
|
|
codeisgreat joined #rest |
| 05:20 |
|
|
rj11 joined #rest |
| 05:39 |
|
|
Davey joined #rest |
| 05:39 |
|
|
Davey joined #rest |
| 05:48 |
|
|
dreamdust joined #rest |
| 05:48 |
|
|
gluegadget joined #rest |
| 05:48 |
|
|
jgornick joined #rest |
| 05:48 |
|
|
rickharrison joined #rest |
| 05:48 |
|
|
blindscreen joined #rest |
| 05:49 |
|
|
jgornick joined #rest |
| 06:00 |
|
|
jgornick joined #rest |
| 06:00 |
|
|
dreamdust joined #rest |
| 06:00 |
|
|
gluegadget joined #rest |
| 06:00 |
|
|
rickharrison joined #rest |
| 06:00 |
|
|
blindscreen joined #rest |
| 06:02 |
|
|
jgornick joined #rest |
| 06:11 |
|
|
lemur joined #rest |
| 07:11 |
|
|
OsRos joined #rest |
| 10:33 |
|
|
Left_Turn joined #rest |
| 11:15 |
|
|
graste joined #rest |
| 11:20 |
|
|
PalyaPix joined #rest |
| 11:31 |
|
|
mezod joined #rest |
| 11:55 |
|
|
proteusguy joined #rest |
| 12:01 |
|
|
mezod joined #rest |
| 12:30 |
|
|
PalyaPix joined #rest |
| 12:41 |
|
|
lemur joined #rest |
| 13:35 |
|
pdurbin |
fumanchu_: have you looked at ElasticSearch URLs? I think they use JSON as query strings but they encode it. |
| 13:39 |
|
|
PalyaPix joined #rest |
| 14:03 |
|
pdurbin |
hmm, I guess I'm thinking of Kibana, which sits in front logstash, which sits on top of elasticsearch |
| 14:03 |
|
pdurbin |
it has URLs like this: http://semicomplete.com/kibana/#eyJzZWFyY2giOiIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjE1IG1pbnV0ZXMiLCJncmFwaG1vZGUiOiJjb3VudCJ9 |
| 14:05 |
|
pdurbin |
echo eyJzZWFyY2giOiIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjE1IG1pbnV0ZXMiLCJncmFwaG1vZGUiOiJjb3VudCJ9 | base64 -d |
| 14:05 |
|
pdurbin |
{"search":"","fields":[],"offset":0,"timeframe":"15 minutes","graphmode":"count"} |
| 14:06 |
|
pdurbin |
fumanchu_: but you're saying you don't base64-encode the json in your query strings? you're just careful? |
| 15:31 |
|
|
PalyaPix joined #rest |
| 16:49 |
|
|
graste joined #rest |
| 16:56 |
|
|
marcoslamuria joined #rest |
| 16:59 |
|
|
marcoslamuria joined #rest |
| 17:02 |
|
fumanchu_ |
pdurbin: right. we urlencode them, of course, to make a valid URI, hence all the ++++ if you're not careful about indentation |
| 17:06 |
|
pdurbin |
fumanchu_: ok, so you urlencode the JSON but you don't base64 encode it. so you can still read the JSON in the URL |
| 17:06 |
|
fumanchu_ |
correct |
| 17:07 |
|
pdurbin |
sounds like a good way to do it |
| 17:07 |
|
fumanchu_ |
(mostly, bounding brackets and quotes and commas get hard to read, but the payload values are plain) |
| 17:07 |
|
fumanchu_ |
%7B%7D etc |
| 17:08 |
|
pdurbin |
yeah. not much you can do. gotta do something to make the JSON valid in a URL |
| 17:14 |
|
|
tr3online joined #rest |
| 17:24 |
|
|
PalyaPix joined #rest |
| 17:58 |
|
|
rue_XIV joined #rest |
| 17:59 |
|
|
rue_ joined #rest |
| 18:30 |
|
|
znn joined #rest |
| 18:49 |
|
|
tr3online joined #rest |
| 18:50 |
|
|
PalyaPix joined #rest |
| 19:46 |
|
|
_ollie joined #rest |
| 19:56 |
|
|
PalyaPix joined #rest |
| 20:24 |
|
|
marcoslamuria joined #rest |
| 20:37 |
|
|
PalyaPix joined #rest |
| 21:20 |
|
|
tr3onlin_ joined #rest |
| 21:21 |
|
|
marcoslamuria joined #rest |
| 21:41 |
|
|
lemur joined #rest |
| 22:26 |
|
|
marcoslamuria joined #rest |
| 23:56 |
|
|
cigarshark joined #rest |
