Anyone home? (Bump =D I've looked at the man pages and found examples in the archive but I can't get a simple URL match to work for the second backend.
Please see my first post: ________________________________ From: Pound Rproxy <[email protected]> To: pound <[email protected]> Sent: Mon, March 14, 2011 4:27:51 PM Subject: [Pound Mailing List] URL match to go to a Backend - how? Hi, I've just got https working for one backend (141), and I'm now trying to get it working for an extra backend (142) - but by matching URL. The end result I need is for: https:192.168.1.140/myapp to show content from: 192.168.1.142:8083/myapp The following config isn't doing this: ListenHTTPS Address 192.168.1.140 Port 443 Cert "/usr/etc/server.pem" ClientCert 2 2 CAlist "/usr/etc/my_CA_list.pem" VerifyList "/usr/etc/my_CA.pem" LogLevel 2 Service BackEnd Address 192.168.1.141 Port 8080 End End Service URL "^/myapp" BackEnd Address 192.168.1.142 Port 8083 End End End I've tried also tried: URL "^/myapp.*" and URL "/myapp.*" There is content in 192.168.1.142:8083/myapp, so I'm not missing that part. But it's likely I'm missing something that's very obvious, and I'm really excited about this feature of Pound and need it. Please show me where I am going wrong or how to better test to find where I am going wrong. Thanks -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
