[akka-user] Disable relative URI parsing in Akka HTTP?

2015-12-01 Thread Tim Harper
Quick and easy question (I hope). If Akka HTTP routes a request such as "/path/to/../resource", then prior to routing the URL is normalized to "/path/resource". Is there a way to disable this normalization behavior? I see that there's a way to enable a special header

Re: [akka-user] Disable relative URI parsing in Akka HTTP?

2015-12-01 Thread Konrad Malawski
Did you see: # Enables/disables the addition of a `Raw-Request-URI` header holding the # original raw request URI as the client has sent it. akka.http.server.raw-request-uri-header = off Perhaps it would address your need? --  Cheers, Konrad 'ktoso’ Malawski Akka @ Typesafe On 1 December 2015 a

Re: [akka-user] Disable relative URI parsing in Akka HTTP?

2015-12-01 Thread Roland Kuhn
I think he wants to use path matchers to route based on a `..` segment and my gut reaction is «not a good idea». Tim, can you provide a use case? Sent from my iPhone > On 02 Dec 2015, at 00:03, Konrad Malawski > wrote: > > Did you see: > > # Enables/disables the addition of a `Raw-Request-

Re: [akka-user] Disable relative URI parsing in Akka HTTP?

2015-12-08 Thread Tim Harper
I saw the docs, yes (mentioned it in my original post). Use case is I have an api which Acts as a key value store, and rather than passing in the key via a query string param, I'm passing it in via the Path, and would prefer to not have path normalization occur. The raw param will suit my needs

Re: [akka-user] Disable relative URI parsing in Akka HTTP?

2015-12-08 Thread Tim Harper
I saw the docs, yes (mentioned it in my original post). Use case is I have an api which Acts as a key value store, and rather than passing in the key via a query string param, I'm passing it in via the Path, and would prefer to not have path normalization occur. The raw param will suit my needs

Re: [akka-user] Disable relative URI parsing in Akka HTTP?

2015-12-08 Thread Roland Kuhn
Ah, so you’re only cheating a little ;-) > 9 dec 2015 kl. 07:18 skrev Tim Harper : > > I saw the docs, yes (mentioned it in my original post). Use case is I have an > api which Acts as a key value store, and rather than passing in the key via a > query string param, I'm passing it in via the Pa