Honor X-Forwarded-Prefix header

[Shayan-To]

I'm using Caddy behind an Nginx reverse proxy. Nginx is stripping a path prefix (e.g. /blog), and setting X-Forwarded-Prefix header (e.g. X-Forwarded-Prefix: /blog).

My problem is that when Caddy is trying to return a redirect response (30X), the location does not honor the path prefix. For example if I try to get /blog/wp-content, it is redirected to /wp-content/ and not /blog/wp-content/.

[mholt]

#Thanks for opening an issue! We'll look into this.

It's not immediately clear to me what is going on, so I'll need your help to understand it better.

Ideally, we need to be able to reproduce the bug in the most minimal way possible using the latest version of Caddy. This allows us to write regression tests to verify the fix is working. If we can't reproduce it, then you'll have to test our changes for us until it's fixed -- and then we can't add test cases, either.

I've attached a template below that will help make this easier and faster! This will require some effort on your part -- please understand that we will be dedicating time to fix the bug you are reporting if you can just help us understand it and reproduce it easily.

This template will ask for some information you've already provided; that's OK, just fill it out the best you can. :+1: I've also included some helpful tips below the template. Feel free to let me know if you have any questions!

Thank you again for your report, we look forward to resolving it!

Template

## 1. Environment

### 1a. Operating system and version

```
paste here
```


### 1b. Caddy version (run `caddy version` or paste commit SHA)

This should be the latest version of Caddy:

```
paste here
```


## 2. Description

### 2a. What happens (briefly explain what is wrong)




### 2b. Why it's a bug (if it's not obvious)




### 2c. Log output

```
paste terminal output or logs here
```



### 2d. Workaround(s)




### 2e. Relevant links




## 3. Tutorial (minimal steps to reproduce the bug)

Instructions -- please heed otherwise we cannot help you (help us help you!)

1. Environment: Please fill out your OS and Caddy versions, even if you don't think they are relevant. (They are always relevant.) If you built Caddy from source, provide the commit SHA and specify your exact Go version.

2. Description: Describe at a high level what the bug is. What happens? Why is it a bug? Not all bugs are obvious, so convince readers that it's actually a bug.

   • 2c) Log output: Paste terminal output and/or complete logs in a code block. DO NOT REDACT INFORMATION except for credentials. Please enable debug and access logs.
   • 2d) Workaround: What are you doing to work around the problem in the meantime? This can help others who encounter the same problem, until we implement a fix.
   • 2e) Relevant links: Please link to any related issues, pull requests, docs, and/or discussion. This can add crucial context to your report.

3. Tutorial: What are the minimum required specific steps someone needs to take in order to experience the same bug? Your goal here is to make sure that anyone else can have the same experience with the bug as you do. You are writing a tutorial, so make sure to carry it out yourself before posting it. Please:

   • Start with an empty config. Add only the lines/parameters that are absolutely required to reproduce the bug.
   • Do not run Caddy inside containers.
   • Run Caddy manually in your terminal; do not use systemd or other init systems.
   • If making HTTP requests, avoid web browsers. Use a simpler HTTP client instead, like curl.
   • Do not redact any information from your config (except credentials). Domain names are public knowledge and often necessary for quick resolution of an issue!
   • Note that ignoring this advice may result in delays, or even in your issue being closed. 😞 Only actionable issues are kept open, and if there is not enough information or clarity to reproduce the bug, then the report is not actionable.

Example of a tutorial:

Create a config file:

{ ... }

Open terminal and run Caddy:

$ caddy ...

Make an HTTP request:

$ curl ...

Notice that the result is ___ but it should be ___.

[trajano]

Just a guess but can't you use the existing rewrite and header match facilities to do this?

[jdog41]

?

On Sun, Sep 21, 2025, 12:12 PM Archimedes Trajano @.***> wrote:

trajano left a comment (caddyserver/caddy#6908) https://github.com/caddyserver/caddy/issues/6908#issuecomment-3316128345

Just a guess but can't you use the existing rewrite https://caddyserver.com/docs/caddyfile/directives/rewrite and header match facilities to do this?

— Reply to this email directly, view it on GitHub https://github.com/caddyserver/caddy/issues/6908#issuecomment-3316128345, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANPXOPQTLHVLZMTPOVPMCUD3T3MANAVCNFSM6AAAAABZKHRRMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMJWGEZDQMZUGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[Shayan-To]

Apparently, I forgot to close this issue, saying that the problem was actually me not understanding the Caddy configuration of the docker image.

I ended up solving my problem by adding this to my route:

	# From https://frankenphp.dev/docs/config/#caddyfile-config (near the end of the section)
	@canonicalPath {
		file {path}/index.php
		not path */
	}
	redir @canonicalPath {http.request.header.X-Forwarded-Prefix}{path}/ 308