Rewrite URL

In the first case you were sending SSL-terminated (i.e. HTTPS->HTTP) traffic to an SSL port (443) on your servers. You either need to change the server to accept HTTP traffic on port 80 since the BIG-IP is already handling the SSL, or in the virtual server you need to assign a server SSL profile (just use the default one) so that the BIG-IP will re-encrypt the traffic to SSL on the back-side.

 

 

For your first question, if you view the source of the page, are the images referenced as http://autodoc.fiz-karlsuhe.de/img/image.jpg? In other words is the full path specified as opposed to just "/img/image.jpg" or just "image.jpg"? If so, you will need to apply the default stream profile to a virtual server and uncomment the lines near the end of the iRule to allow it to try and modify the actual page contents. This may or may not work (depending on your page) but it is worth a shot.

 

 

For your second question this is the exact behavior you have configured. The whole point of the ProxyPass iRule is to allow the clients to hit an external URL (testf5web.fiz-karlsruhe.de/autodoc) and, without being redirected and without ever seeing the name of the inside host, visit the internal site autodoc.fiz-karlsruhe.de/. You have to decide what you want the browser to show in the URL bar. If you want the browser to show autodoc.fiz-karlsruhe.de/ (and your users can access that by going to http://autodoc.fiz-karlsruhe.de/) then you don't want ProxyPass at all, instead you want to do a simple HTTP Redirect iRule that will redirect http://testf5web.fiz-karlsruhe.de/autodoc/ to http://autodoc.fiz-karlsruhe.de/. A redirect tells the browser "Hey, go to a different URL, here it is". While ProxyPass doesn't say a word to the browser -- it gives the browser the illusion that they are viewing the /autodoc/ subdirectory on your site while on the back-side they are really talking to a different server.