Differences

This shows you the differences between two versions of the page.

Link to this comparison view

irc:1471989600 [2017/05/27 13:44] (current)
Line 1: Line 1:
 +[09:39:31] *** ChanServ sets mode: +o temporalfox
 +
 +[19:11:32] <​samsquanch>​ Can anyone tell me if the unmarshalling from the event bus can be dun in a safer / more elegant way than just casting?
 +
 +[19:11:48] <​samsquanch>​ Coming from a scala background this aspect just feels ultra clunky
 +
 +[20:07:40] <​nat_>​ @Ephemeral I think we found another problem with parameter decoding using URLDecoder
 +
 +[20:27:16] <​nat_>​ it looks like + is allowed in the URL path without special encoding
 +
 +[20:28:17] <​nat_>​ this means that if I have http://​localhost/​wiggle+jimmy and my pattern is /:names, the names should be "​wiggle+jimmy"​ instead of "​wiggle jimmy"
 +
 +[20:59:40] <​nat_>​ ah it seems to be partially fixed by https://​github.com/​vert-x3/​vertx-web/​pull/​408/​files but it is still broken
 +
 +[22:05:17] <​pmlopes>​ @nat wiggle+jimmy should be wiggle jimmy because + is a escape for space, that is the expected behavior
 +
 +[22:38:04] <​nat_>​ @pmlopes, that is not what RFC3986 said https://​tools.ietf.org/​html/​rfc3986#​section-3.3
 +
 +[22:39:04] <​nat_>​ "​!"​ / "​$"​ / "&"​ / "'"​ / "​("​ / "​)" ​   / "​*"​ / "​+"​ / ","​ / ";"​ / "​="​ /  ":"​ / "​@"​ are not supposed to be encoded
 +
 +[22:39:23] <​nat_>​ so it's not supposed to be decoded either
 +
 +[22:41:38] <​nat_>​ Jersey/​JAX-RS goes at a great length to address this issue
 +
 +[23:02:56] <​AlexLehm>​ the person who came up with the encoding of space as + should be severely beaten, I think
 +
 +[23:03:17] <​AlexLehm>​ + is different in the path (before ?) than after ?