Piping Stream to Response Yields Empty Result

[JD-Robbs]

Consider the following example of piping a stream (any stream; but my example uses PDF) to the result object:

@Get("/pdf")
public pdf(@Req() req: Request, @Res() res: Response) {
    let wkhtmltopdf = require("wkhtmltopdf");

    res.setHeader("Content-type", "application/pdf");
    wkhtmltopdf("http://localhost/my/app").pipe(res);
}

Unfortunately, the route simply returns Cannot GET /pdf.

The same code, however, works when conventionally registering the route as below.
I wonder if I'm doing something wrong, or if the piping of streams is not yet supported.

app.get("/test", (req: Request, res: Response) => {
    let wkhtmltopdf = require("wkhtmltopdf");

    res.setHeader("Content-type", "application/pdf");
    wkhtmltopdf("http://localhost/projects/proposely").pipe(res);
});

[pleerock]

I haven't tested pipes support, I need deeper investigation of this issue. Do you know what wkhtmltopdf("...").pipe(res); does inside? Does it use request.send somehow?

btw this is offtopic, but you can use @Header("Content-type", "application/pdf") instead of res.setHeader("Content-type", "application/pdf");

[Diluka]

If I call res.send manually, there must be an error Can't set headers after they are sent.

[felipesabino]

Any news on this? I am having the same issue trying to return a stream with binary data

Error: write after end

[pleerock]

I recommend to use old school res and return using it until I come back to this issue.

[ajmalmsali]

@felipesabino any updates?

[pleerock]

this should be fixed in 0.7.0. If its not please create a new issue.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.