Hello Peter, P. Broennimann <[email protected]> (Di 19 Feb 2013 08:01:50 CET): > Hi there > > I am hosting a site (1 pound instance and 5 own load-balanced application > instances behind). Clients would connect > https://www.mywebsite/html/myapplication.html so Pound is terminating the > SSL -> Everything works like a charm. > > Now I'd like to have the clients connect > https://www.mywebsite/myapplication.html. I read that I could do this using > a separate URL rewrite engine. > > 1) Where would this rewrite engine be placed? Before or after Pound? I am > concerned about where SSL would be terminated.
Outside of pound (between the client and Pound) you can't do any rewriting - it's HTTPS. (Except you break the SSL …) The only place I can think of it, is between Pound and the backends, including Pound and the backends. Pound can't do the rewriting (http://www.mail-archive.com/[email protected]/msg01230.html), but the backends could do - it depends on your web server. Apache can do the rewriting. > 2) Does this have to be a webserver (apache) or are there other smaller > tools available to just do the URL rewriting (I am running Debian)? Never used anything else than apache, but probably nginx. But, if you're familiar with configuring Apache, I'd stay with apache. From my POV you can configure just some (1..2) of your backends, and then use Pound to send all „wrong“ requests to exactly these boxes, asking for the redirect. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: 7CBF764A - gnupg fingerprint: 9288 F17D BBF9 9625 5ABC 285C 26A9 687E 7CBF 764A - (gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B)-
signature.asc
Description: Digital signature
