http listener not listening on "invalid" uri's

Oct 9, 2015 at 7:19 AM
Edited Oct 9, 2015 at 7:21 AM
Hey Guys,

I'm using the listener on localhost and nearly everything works smoothly, but during testing I now ran into a problem. Whenever I'm trying to access the listener through in invalid uri scheme, the listener isn't notified about my request and therefore nothing happens.

In particular I'm trying to request the uri
unencoded and nothing happens! No response, no exception, nothing! Encoded as
the request is noticed and correctly responded to.

Is this behaviour expected? If so, how is it possible to implement any service-sided feedback for requests on invalid uri's or is any client always responsible for ensuring the uri being valid?

Thanks in advance,
Oct 9, 2015 at 8:31 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Oct 9, 2015 at 8:33 PM
hey FredericSt

This looks like a bug in our http_listener. We are not passing the request to the handler in such cases.
I have opened a workitem for this. However we may not be able to get to it in the near future.