Rewrite profile
Hello guys, So as proxypass will be soon removed I am creating rewrite profile as substitute. However it is not working 😞 so this is my scenario (just sample) will be redirected to Configuration Rule Type: Both Client: /home/ Server: http://www.f5.com/ My proxypass configuration for Data group was www.cathy.com/home := www.f5.com/ HTTP_F5_pool My rewrite profile is not working but my proxypass is working. I think the difference is on the pool? Can anyone check my config. Am I missing something? Thank you!238Views0likes1CommentRewrite profile - any better way?
Hi, I wonder is there is any simpler way to achieve something described below: Scenario: Single VS - IP mapped to few external FQDNs Each external FQDN maps to virtual host on the same backend server (so traffic accepted only if there is Host header match in request send from BIG-IP to backend) There is possibility that some links returned from backend (in content) are not relative and can use backend srv FQDN. Setup: Local Traffic Policy forwarding traffic to appropriate pool based on host header in request from client - sure it could be one pool but because FQDN nodes has to be used I guess separate pools are needed - or not? Then Rewrite profile with URI rules for each ext FQDN to int FQDN with Rewrite Header, Rewrite content set, like * -> * -> * -> * and so on When redirect from http to https (send from backend) is needed then another Rewrite profile is necessary for HTTPS VS: * -> * -> * -> * and so on It is working OK but requires plenty of objects to be configured, everything has to be entered by hand, in few places and cause a lot of work and possibility to make mistake :-( Is there any other way (simpler, less error prone) to achieve the same goal? Piotr599Views0likes4CommentsNGINX Migration, Rewrite Profile: Is there another way?
We are migrating, as part of a project, a big NGINX implementation to an F5. Basically, it would assume the role of a reverse proxy. The two biggest things the NGINX does are: Translating from external hosts (www.example.com) to internal hosts (www.example.local) Load balancing between different back-end servers, depending on the URI. For the first point: There are a BUNCH of translations. We're using a rewrite profile. Sometimes, www.example.com/ translates to www.example.local/, and www.example.com/app1/ translates to www.example2.com/app1. And, on a single rewrite profile, there are, I think, more than 50 rules. Is there a better way of doing this? Should we really modify back-end servers to accept both hosts, external and internal? And, how do we deal with URI's with no trailing slash? If they have none, it won't match the rewrite rule. Should we add 301 respond to each and every URI? The second: Should we use policies or iRules? I've got to confess, we have already big iRules, separated with procs and the like. So, migrating that to policies would be a pain in the ass. EDIT: One more question: We have different client side URL, that need to be rewritten to the same server. www.example.com/app1 and www.example.com/app2 to www.example.local/. However, for some reason, rewrite profile does not allow for this. How can we achieve it?589Views0likes1CommentLTM Rewrite Profile - Is there any way to make the matching case-insensitive?
Is there any way to make the LTM Rewrite Profile case insensitive when it does matching? I am using a rewrite profile based on rewrite-uri-translation to do very simple remapping of external directories to internal servers/directories, and it is running in URI-Translation mode, not Portal mode. This scenario is similar to Apache mod_proxy/mod_rewrite functionality, and F5 recommends using a combination of the LTM Traffic Policy and the Rewrite Profile to do this. However, I'm running into a case sensitivity problem. In Apache, the NC (no-case) flag is nearly always used to provide for case insensitive matching of rewrite rules, and rules from mod_proxy like ProxyPassReverse seem to be by default case insensitive. Similarly, the LTM Traffic Policy is by default case insensitive when it comes to the conditions inside policy rules such as matching URI paths. But unfortunately, the LTM Rewrite Profile is case sensitive, and worse, I can't seem to find any way to turn it off. So a rewrite rule that is supposed to rewrite requests for paths starting with /example/, would not match if the user sent in a path starting with /ExAmPle/. What I Am Looking For In An Answer: I am looking for a definite answer as to how you turn off case sensitivity in the rewrite profile. Alternatively, an answer saying it is not possible is acceptable, as long as it has somehow been confirmed to be true. I'm not looking for iRules or other ways to do this. I know there are other ways to do this, but I would really like to see if this way is possible first, because it would be by far the easiest way for my end users (who aren't necessarily coders or iRule masters) to maintain.756Views0likes3CommentsURI Rule in Rewrite profile disable Server SSL profile?
Hi, Setup: TMOS 12.1.2HF1 VS listening on port 80 Server SSL profile attached Rewrite profile settings: Rewrite Mode: URI Translation Parent Profile: rewrite Request Settings: Rewrite Headers Response Settings: Rewrite Headers, Rewrite Content URI Rule: Client: http://www.domainA.com/ Server: http://www.domainB.com/ Pool member set to port 443 Whith above settings SSL is disabled on backend - client HTTP request on port 80 is passed as HTTP request on port 443 on backend side. There is no SSL Handshake performed. Result: backend server do not respond If URI Rule is changed to: Client: http://www.domainA.com/ Server: https:// Everything starts to work, BIG-IP is starting SSL Handshake and backend is accepting connection. Is that by design? So protocol definition in URI Rule is defining protocol used on backend - in other words disables Server SSL profile when set to http for Server? Piotr606Views0likes9Commentssome image content cant be load and work properly
dear all, i have deployed big ip ltm on my customer, the function of this appliance is to offload and load balance the portal server (used to login to the customer site). the problem occur when we offloading the https, the whole page seems broken. i try to used this link https://devcentral.f5.com/codeshare?sid=573, the whole page still broken and the authentication always failed.however, some image content can be loaded and work properly. after that i try to used stream profile, but not used rewrite profile that i talk before, with http profile response chunking is re-chunk. the page can now be loaded and work properly, neither the authentication, but unfortunately some image still broken. any suggestion about this problem? thank you554Views0likes4CommentsHost Rewrite or iRule?
Hello All, I am a total noob when it comes to out F5 BIG-IP LTM. I know enough to do some pretty basis stuff. I have been asked to do something that I have never had to do before. My company has a need do what I think is a host URI rewrite or "something" Basically, I need to : externalSiteA.company.com --> F5 vip/vs "repoints it to" --> internalSiteXYZ/aba/blabla/12345 ( This is being a very specific inside URL to an application. Does this make sense. Any help would be greatly appreciated!!!! Thank you.367Views0likes6Comments