Fork me on GitHub
#funcool
<
2016-06-10
>
niwinz04:06:36

nice, I'll try to investigate about it, thanks @kardan

kardan04:06:58

@niwinz I wonder if it’s not Ratpack that does not like the cookie value

niwinz05:06:05

it is possible, but ratpack as is does nothing with cookies, so it can be completly possible that netty is the cause also

kardan05:06:21

I don’t know much about this

niwinz05:06:22

I'll try to research about it today

kardan05:06:29

No stress from my side

niwinz05:06:41

ok, nice to know

kardan05:06:53

It was just that I made a mistake trying to store a jws token in a cookie

kardan05:06:12

hence tried to store “Token <token” in a cookie

niwinz12:06:11

@kardan: seems like cookie value is very limited in allowed characters

niwinz12:06:42

and ratpack uses a netty's strict validation of cookies

niwinz12:06:01

that causes that netty rejects the cookies with spaces and other chars...

niwinz12:06:33

related rfc

niwinz12:06:55

and related SO response

niwinz12:06:09

I'll update the documentation with this

kardan12:06:25

@niwinz: ok, thanks for the update. I was a bit confused to get the "No response sent for POST request to” error

niwinz13:06:46

This is final exception caused by an other internal exception

niwinz13:06:03

I don't know if other exceptions are logged or not

niwinz13:06:33

if not maybe you need add an optional dependency to [org.slf4j/slf4j-simple "1.7.21" :scope "provided"]

niwinz13:06:09

if you run the tests with your modifcation of the cookie test

niwinz13:06:51

you will see that the exception chain is pretty big and the no response is caused by

kardan13:06:13

Ah ok, will do. Thanks for the explanation!

niwinz13:06:14

glad to help!