0.9.3 streaming interface throws null pointer at runtime about reboot HOT 3 CLOSED

I'll have a quick look into this so see if I can't fix it myself

from reboot.

I got rid of the potential for a null pointer with this commit but I found something strange. This request return a 404 in 0.9.3 and a 200 in 0.9.2. I did a quick scan of the changes in this release and I think something broke with the path encoding along the way.

Check this out

In the latest the path gets encoded as

scala> val r = :/("stream.meetup.com") / "2" / "rsvps"
r: com.ning.http.client.RequestBuilder = com.ning.http.client.RequestBuilder@ecdede5

scala> r.build()
res0: com.ning.http.client.Request = http://stream.meetup.com/%32/rsvps GET

But in 0.9.2 the path gets encoded as

scala> val r = :/("stream.meetup.com") / "2" / "rsvps"
r: com.ning.http.client.RequestBuilder = com.ning.http.client.RequestBuilder@48d942c2

scala> r.build()
res0: com.ning.http.client.Request = http://stream.meetup.com/2/rsvps   GET

Should I open a second gh issue and close this one or is this expected behavior for the new path encoding stuff? The fix I just pushed upsteam does a potential bug but just allowed me to find this other issue.

from reboot.

killed two birds with two stones in one issue. the issue was that numerics were not in the unreserved list of path segment chars. They are now. Crisis averted.

from reboot.