Arpad Ryszka

my understanding is: `"\\"` in eskip is parsed to `"\\"` go internal, which is fine `"\."` in eskip is parsed to `"\\."` go internal, which is wrong i agree that...

another example where the parsing doesn't work as expected: ``` Path("/robots.txt") -> setResponseHeader("Content-Type", "text/plain") -> inlineContent("User-agent: *\r\nAllow: /graphql\r\nAllow: /graphql/*\r\nDisallow: /\r\n") -> status(200) -> ``` In the above route \r and...

I am strongly against this. Consider it this way: when a backend returns a 500, and the proxy successfully proxies this result, the proxy didn't fail, ergo it is not...

the use case is valid, but there alternative approaches. I still would avoid going against the OpenTracing semantics. Instead of using the well defined `error` tag, I would set a...

as we already discussed, one possible solution can be to use a `\` based escape style. E.g: `\:` In this case the main caveat is that `\\` should also become...

one more caveat: we often put these expressions into YAML documents in Kubernetes manifests. Using `\` there can lead to various confusion. E.g if `\:` means `:` and `\\` means...

> ...and reduce prohibited paths to only those where segments start with : or *. Sounds like a simple pragmatic solution, though contains the future problem when somebody wants to...

i was working on this project: https://github.com/aryszka/forget with skipper group cache in mind. The missing point was the swarm communication to maintain a hashring of the skipper instances. The nice...

that's true. Right now this is WIP. We just discussed that we should start with converting the pool/filter instance setup to a shared global pool on the spec, where we...