when HTTP_REQUEST {
set URI [string tolower [HTTP::uri]]
if {$URI starts_with "/m/" }{
set NEW_URI [string range [HTTP::uri] 2 end]
HTTP::respond 301 Location http://www.domain.com$NEW_URI
}
}
$ curl -Ik http://10.10.10.10/m/URI
HTTP/1.0 301 Moved Permanently
Location: http://www.domain.com/URI
Server: BigIP
Connection: Keep-Alive
Content-Length: 0
Replacing
set NEW_URI [string range [HTTP::uri] 2 end]
with
set NEW_URI [string trimleft [HTTP::uri] /m/]
will provide the following output:
$ curl -Ik http://10.10.10.10/m/URI
HTTP/1.0 301 Moved Permanently
Location: http://www.domain.comURI
Server: BigIP
Connection: Keep-Alive
Content-Length: 0
Note the lack of “/” in the “Location” header, just before the start of URI.
In order to retain the “/”, I did a string trimleft with “/m” instead of “/m/” i.e.,
set NEW_URI [string trimleft [HTTP::uri] /m]
instead of
set NEW_URI [string trimleft [HTTP::uri] /m/]
However, the result was the same.
Based on this devcentral article, it looks like “string range” is a better option as “string trim” tends to trim individual characters as instead of the “string of characters”.
Another issue to remember is that if we use “string trim”, we get the following output:
$ curl -Ik http://10.10.10.10/m/mURI
HTTP/1.0 301 Moved Permanently
Location: http://www.domain.comURI
Server: BigIP
Connection: Keep-Alive
Content-Length: 0
and “string range” provides the following:
$ curl -Ik http://10.10.10.10/m/mURI
HTTP/1.0 301 Moved Permanently
Location: http://www.domain.com/mURI
Server: BigIP
Connection: Keep-Alive
Content-Length: 0
So, if you are just looking to remove specific “string of characters”, “string range” is a better option based on testing on 11.x code version.