Mika Tammi

I'm encountering this same issue. The API expects to have a trailing slash, and forwarding causes two requests to be generated, which is a problem because we would like to...

> To get rid of extra argument one can define new combinator instead of `Capture "trailing" Unit` > > ```haskell > type Endpoint = ... :> TrailingSlash :> Post ......

> data EmptyPiece = EmptyPiece > > instance ToHttpApiData EmptyPiece where > toUrlPiece EmptyPiece = "" > > instance FromHttpApiData EmptyPiece where > parseUrlPiece = \case > "" -> Right...

I guess the reason why the above example works on the client side, but not on the server side, is this: https://github.com/haskell-servant/servant/blob/2323906080e50fc2774cd1b43bc59548a90152ed/servant-client-core/src/Servant/Client/Core/BaseUrl.hs#L135 parseBaseUrl function used in the client strips the...

> I don't think `parseBaseUrl` is used for routing. IIUC it is used for getting hostname and path prefix, but not for parsing path piece. You're right, I even went...

It is probably worth noting that servant-server seems to treat URI's with and without the trailing slash as the same thing. If we could define the HasServer instance in a...

I'm also seeing this: ``` warning: error: unable to download 'http://172.18.8.142:5000/bqnisnimwjiaki9376232b1jlydz3qn2.narinfo': Server returned nothing (no headers, no data) (52); retrying in 334 ms warning: error: unable to download 'http://172.18.8.142:5000/bqnisnimwjiaki9376232b1jlydz3qn2.narinfo': Server...

Moved to @Mic92 's fork for now https://github.com/Mic92/nix-serve-ng/commits/fix-build Until I change this system to a flake-based configuration where I can override nixpkgs in the inputs

I have to double check this because looks like with latest versions the builds work again, but I haven't tested the functionality

My build is only using QEMU at the moment, didn't try other hypervisors yet