| Time |
S |
Nick |
Message |
| 00:05 |
|
|
quimrstorres joined #rest |
| 00:23 |
|
|
quimrstorres joined #rest |
| 01:24 |
|
|
quimrstorres joined #rest |
| 02:24 |
|
|
quimrstorres joined #rest |
| 03:25 |
|
|
quimrstorres joined #rest |
| 04:26 |
|
|
quimrstorres joined #rest |
| 05:27 |
|
|
quimrstorres joined #rest |
| 06:33 |
|
|
alxbl joined #rest |
| 07:28 |
|
|
quimrstorres joined #rest |
| 07:47 |
|
|
Left_Turn joined #rest |
| 08:29 |
|
|
quimrstorres joined #rest |
| 09:04 |
|
|
Left_Turn joined #rest |
| 09:04 |
|
|
quimrstorres joined #rest |
| 09:20 |
|
|
quimrstorres joined #rest |
| 09:30 |
|
|
quimrstorres joined #rest |
| 09:40 |
|
|
quimrstorres joined #rest |
| 09:43 |
|
|
quimrstorres joined #rest |
| 09:47 |
|
|
quimrstorres joined #rest |
| 09:59 |
|
|
sll19 joined #rest |
| 10:00 |
|
sll19 |
cookie-based server-side sessions being non-rest, how do i maintain a user session for a REST-style web serivce? What are options to Http authentication + SSL? Thx! |
| 10:48 |
|
|
quimrstorres joined #rest |
| 10:53 |
|
pdurbin |
auth comes up so much |
| 11:16 |
|
|
mezod joined #rest |
| 12:31 |
|
|
quimrstorres joined #rest |
| 12:38 |
|
|
huckleberry78 joined #rest |
| 12:52 |
|
|
quimrstorres joined #rest |
| 13:15 |
|
|
shrink0r joined #rest |
| 13:41 |
|
|
quimrstorres joined #rest |
| 14:15 |
|
|
hucklebe_ joined #rest |
| 15:19 |
|
|
huckleberry78 joined #rest |
| 17:03 |
|
trygvis |
pdurbin: yeah |
| 17:04 |
|
trygvis |
someone should write up a blog post on the different styles used :) |
| 17:04 |
|
pdurbin |
should this channel have a wiki or something? |
| 17:11 |
|
trygvis |
there's always the one in the topic |
| 17:11 |
|
trygvis |
but that one is going to die soon |
| 17:12 |
|
trygvis |
the rest mailing list also seems to have died out a bit |
| 17:14 |
|
pdurbin |
huh, I've never even looked at the wiki at https://code.google.com/p/implementing-rest/ before |
| 17:15 |
|
pdurbin |
of course, soon enough that wiki will be gone... "Project Hosting on Google Code will close on January 25th, 2016" https://code.google.com |
| 17:16 |
|
trygvis |
exactly |
| 17:17 |
|
pdurbin |
I don't know if anyone here helped write anything there. The last update was almost two years ago. |
| 17:17 |
|
trygvis |
I think something wikipedia-like could be useful |
| 17:17 |
|
|
DrCode joined #rest |
| 17:18 |
|
pdurbin |
or just a website. I don't know |
| 17:19 |
|
trygvis |
yeah, but I think lowering the bar for contribution is always useful |
| 17:20 |
|
trygvis |
I could host and maintain an instance of mediawiki or a site if people would commit to contributing :) |
| 17:21 |
|
pdurbin |
I'm not a *huge* fan of mediawiki but sure, something. |
| 17:23 |
|
pdurbin |
I'm definitely commit. |
| 17:23 |
|
pdurbin |
I'd |
| 17:27 |
|
trygvis |
are there any other good open source wikis? |
| 17:27 |
|
trygvis |
where good is "better than mediawiki" |
| 17:28 |
|
pdurbin |
I use http://ikiwiki.info |
| 17:29 |
|
trygvis |
wow, that looks even worse than mediawiki! |
| 17:29 |
|
trygvis |
is the editor and stuff any better? |
| 17:30 |
|
trygvis |
packages in debian is always a plus |
| 17:32 |
|
trygvis |
login with google++ is nice |
| 17:38 |
|
pdurbin |
I like it for a few reasons: |
| 17:38 |
|
pdurbin |
- backed by git |
| 17:38 |
|
pdurbin |
- can write in markdown |
| 17:38 |
|
pdurbin |
- can organize contents into folders (and subfolders) |
| 17:39 |
|
pdurbin |
- can be made to look decent if you care to: http://www.dragonflybsd.org |
| 17:40 |
|
trygvis |
yeah, it's not bad at all |
| 17:41 |
|
pdurbin |
ikiwiki has a web interface for editing but I don't use it |
| 17:46 |
|
trygvis |
hm, it's kinda useless if people can't edit it through the web interface, isn't it? |
| 17:50 |
|
pdurbin |
ikiwiki is backed by git. who makes git commits using GitHub's web interface? :) |
| 17:51 |
|
trygvis |
dunno, is that easy enough for people to actually use it? |
| 17:52 |
|
pdurbin |
maybe a high bar is better ;) |
| 17:52 |
|
trygvis |
perhaps, some people like that others look at it before deploying |
| 17:52 |
|
trygvis |
dunno |
| 17:53 |
|
pdurbin |
maybe an installation of http://discourse.org would be better |
| 17:54 |
|
pdurbin |
trygvis: are you set up to host anything other than PHP? |
| 17:55 |
|
trygvis |
sure |
| 17:55 |
|
trygvis |
ikiwiki is perl :) |
| 17:55 |
|
pdurbin |
yeah. and discourse is ruby |
| 17:56 |
|
trygvis |
I've never used discourse |
| 17:56 |
|
trygvis |
the nice thing with mediawiki and ikiwiki is that they're in debian so they will be kept up to date |
| 17:58 |
|
pdurbin |
oh, sure. and installing discourse is pretty hard, last I heard |
| 17:58 |
|
trygvis |
I can imagine; all I find are installation instructions with docker :) |
| 17:59 |
|
pdurbin |
the ikiwiki web interface works fine. I just don't bother with it since it's just me at http://wiki.greptilian.com (and I haven't bothered to make it look pretty) |
| 18:00 |
|
trygvis |
I'm trying to figure out ikiwiki now |
| 18:00 |
|
trygvis |
I did a major look around to look for a wiki/blog combination a while back, I wonder why I left out ikiwiki |
| 18:00 |
|
pdurbin |
trygvis: here's my ikiwiki setup script if it's of interest: https://github.com/pdurbin/greptilian-vagrant/blob/master/modules/server1/files/usr/local/greptilian/bin/wiki-setup |
| 18:10 |
|
trygvis |
thanks |
| 18:10 |
|
trygvis |
you're in debian: /usr/share/doc/ikiwiki/html/users/pdurbin.html :) |
| 18:20 |
|
pdurbin |
! |
| 18:20 |
|
pdurbin |
weird. ubuntu too: http://packages.ubuntu.com/trusty/all/ikiwiki/filelist |
| 18:22 |
|
pdurbin |
I assume the content of that file is this: http://ikiwiki.info/users/pdurbin/ |
| 18:23 |
|
trygvis |
yep |
| 18:30 |
|
pdurbin |
trygvis: if you get ikiwiki set up, it would be awesome if we could all update via git. for me the web interface is optional :) |
| 18:33 |
|
trygvis |
https://github.com/trygvis/rest-wiki |
| 18:34 |
|
trygvis |
go crazy! :) |
| 19:07 |
|
trygvis |
https://trygvis.io/rest-wiki/ |
| 19:08 |
|
trygvis |
locally chrome is showing me an ssl warning, but I can't figure out if it just a problem for me or wtf is going on |
| 20:08 |
|
|
quimrstorres joined #rest |
| 20:24 |
|
|
shrink0r joined #rest |
| 21:14 |
|
|
begriffs joined #rest |
| 21:18 |
|
|
begriffs joined #rest |
| 21:31 |
|
|
imanc_ left #rest |
| 21:49 |
|
pdurbin |
trygvis: that was fast! sorry, ran out to a birthday party (trampoline place). so ssl warnings here |
| 22:32 |
|
|
quimrstorres joined #rest |
| 22:49 |
|
|
quimrstorres joined #rest |
| 22:49 |
|
|
fumanchu_ joined #rest |
| 23:19 |
|
|
dcrk joined #rest |
| 23:21 |
|
dcrk |
Hi |
| 23:21 |
|
dcrk |
Do you think excess parameters should result in 403? |
| 23:31 |
|
pdurbin |
you could just ignore extra query parameters your app doesn't pay attention to |
| 23:36 |
|
|
quimrstorres joined #rest |
| 23:38 |
|
dcrk |
pdurbin: that is currently what I do, but what about cases where the parameter is meaningful but it's use is forbidden? |
| 23:38 |
|
dcrk |
say I'm a client of Githubs API and I try to get all the repos that belongs to a b.com but github forbids email filtering |
| 23:42 |
|
dcrk |
oh, got some help :) seems like 400 is the one |
| 23:45 |
|
pdurbin |
well, there's 401 and 403 also |
| 23:46 |
|
pdurbin |
but yeah, sounds like 400 might be better |
| 23:51 |
|
dcrk |
yep, will use that one. thank you! |
