Replies: 2 comments 2 replies
-
|
Hello. Just to make sure I get it right: by "redirecting a request" you mean internal routing to another backend, not redirecting in HTTP sense (301, 302 response code), right? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi Sergey,Yes, you are right and sorry if my wording was imprecise. If the web server at the target backend answers with 421, pound should route the original request to another specified backend.Thanks for answering,Martin Am 16.02.2026 um 20:59 schrieb Sergey Poznyakoff ***@***.***>:
Hello. Just to make sure I get it right: by "redirecting a request" you mean internal routing to another backend, not redirecting in HTTP sense (301, 302 response code), right?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is it possible to redirect a request to another backend which was returned from original backend with a specific response status code?
Eg. I have a backend which has some business logic to respond with status code 421 (Misdirect Request) to some ill-formed requests. In that case, I want
poundto hand over the request to a different backend which is configured for that requests. Nginx has some functionality to redirect to a fallback location dependend on the error code and although I looked through the pound documentation, I could not find a similar functionality. Did I miss it?Beta Was this translation helpful? Give feedback.
All reactions