Forum Discussion
Redirecting with dynamic URI content
I am trying to find an example of a redirection that takes into account the node passing dynamic variables back to the client upon initial request. If I use the [HTTP::uri] param in the normal redirect from 80 to 443, it truncated the dynamic variables. Is there a provision for telling the redirect to add space to the redirect?
For example
if { [HTTP::uri] starts_with "/uri1/" } {
HTTP::redirect "https://[[HTTP::host][HTTP::uri] 20]"
I know that isnt correct but you get the idea. adding the next 20 characters at the end of the uri that was used as the trigger.
I hope that makes sense.
TIA
1 Reply
- hoolio
Cirrostratus
Hi,
Can you provide a sanitized example URI the client requests over HTTP and what it's getting truncated to after the redirect to HTTPS?
[HTTP::uri] should be the full URI that the client sends in its request so I'm not sure I see the issue.
Aaron
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com