Can I use custom pipeline instead of default

[rajcspsg]

Hi,

This is the question -

The examples for starting the server in this project always using Server.make.
If I want to use some custom http pipeline , How can I achieve the same?

[rajcspsg]

Let me add more details to this issue -

the client can send requests in payload compressed based on the content-encoding header. For example, if the contents are compressed in gzipped format, then the content-encoding header would be gzip. Netty provides HttpContentDecompressor channel handler for this feature.

Similarly the server can also send response in compressed format based on the Accept-Encoding header in the request. For this Netty provides HttpContentCompressor channelHandler for this feature.

I've an example here. The code is on github here. you can run the project by using gradle just-netty:runMain to run the server. The example of client to call the server is here

try(CloseableHttpClient httpclient = HttpClients.createDefault()) {
        HttpPost httppost = new HttpPost("http://localhost:5880/test");
        String payload = "{ \"test\" : 1 }";
        EntityBuilder builder = EntityBuilder.create().gzipCompress().setContentEncoding("gzip").chunked().setText(payload);
        HttpEntity entity = builder.build();
        httppost.setEntity(entity);
        System.out.println();
        httppost.setHeader("Accept-Encoding", "gzip,deflate");
        httppost.setHeader("Content-Encoding", "gzip");
        System.out.println("Executing request: " + httppost.getRequestLine());
        CloseableHttpResponse response = httpclient.execute(httppost);
        try {
            System.out.println("----------------------------------------");
            System.out.println(response.getStatusLine());
            System.out.println(EntityUtils.toString(response.getEntity()));
        } finally {
            response.close();
        }
    }

In my current organization we use HttpContentCompressor and HttpContentDecompressor in our server and also has some additional handler in pipeline.

IMHO, zio-http should allow users to provide option for defining custom HttpPipeline. In cases if the users didn't provide additional pipeline , then Server.make should use default pipeline.

Please let me know if I'm not clear in this problem description.

[tusharmath]

This seems like something we should have in ZIO Http.