On Sat, Dec 19, 2009 at 05:31:24PM +0100, Henrik Sarvell wrote:
wonder about is the part where a normal request would be split and
its keys =3D values would parsed. Is that part enough or is there
something else happening in the big/original flow?
I would check for the initial POST, so that
In this special case I don't need to extract url parameters just the
POST contents in the case of verification.
So I'll incorporate the POST match and give it a try.
On Sun, Dec 20, 2009 at 8:52 AM, Alexander Burger a...@software-lab.de wro=
te:
On Sat, Dec 19, 2009 at 05:31:24PM +0100, Henrik
Apparently it was a GET request but I managed to parse it.
The problem now is that it seems like the prints are on the wrong
channel, before when I was using the normal http etc in the @pubsub
function I didn't get headers printed to my terminal for instance
which I'm getting now. If I only can
On Sun, Dec 20, 2009 at 01:59:59PM +0100, Henrik Sarvell wrote:
Apparently it was a GET request but I managed to parse it.
...
(while (setq L (line))
(cond
((match '(G E T @U H T T
P / 1 . @Y) L)
