Is there support for X-Accel/X-Sendfile in Caddy 2 and if so how would I enable this in the Caddyfile, in Caddy 1 there’s internal without any arguments but I can’t find the equivalent for Caddy 2.

Caddy doesn’t specifically handle that header. What exactly are you trying to achieve? It’s likely possible regardless. Please be as specific as possible so that we have a clear idea of what you need.

My understanding is that X-Accel is an nginx-specific behavior. So I second Francis’ question: what are you actually trying to achieve? I almost guarantee that Caddy 2 can do it (and if not already, then soon). Just need to know what it is.

X-Accel/X-Sendfile headers are intercepted by the webserver and serve whatever file is specified in the header, without redirecting the user.

Yeah, you can probably just do that with rewrite and a header matcher. I feel that the header is probably unnecessary and you could do this more simply anyways. Could you give us a specific example of a request and the expected response?

See one of the many blogposts on the subject, there needs to be a match on a response header from the backend for which there doesn’t seem to be an available matcher? [image] Nginx X-Accel Explained My team was working on a CMS solution based on Django, and we needed to have private fil…

Oh, I see. This is to rewrite a response to serve a static file. Hmm. I’m not sure that’s currently possible, but I think it would be pretty easy to write a plugin that acts as response middleware to do this! See the docs on extending Caddy [image] Extending Caddy - Caddy Documentation …

The module would have to be designed to be added to an existing configuration using the core reverse_proxy implementation, wrap the response, and inspect it for an X-Accel-Redirect header. Then it’s just an if statement - either discard the reverse proxy response and serve the file, or preserve the…

It’s on my TODO list to write a handler that can wrap the response and execute an arbitrary route, either after the headers are written or the whole body… that should be able to implement the functionality then, right?

Yes, assuming we can inspect details of the response as part of that route, theoretically we could just use that handler and have it execute a route that rewrites to exactly the file we want (based on the response header) and serves it via the core file_server. Might look something like this in the…

Hmm, that syntax is mostly for request matchers, not response matchers. Response matchers aren’t really a thing outside of handlers that are designed to capture the responses. I don’t know what the Caddyfile would like yet, I seldom think of that before the underlying JSON (since Caddy doesn’t actu…

Caddy Community

[Caddy 2] X-Sendfile/X-Accel support?

Help

show post in topic

Home
Categories
Guidelines
Terms of Service

Powered by Discourse, best viewed with JavaScript enabled