RE: Ignore all filters except ssl one
Title: RE: Ignore all filters except ssl one resending mail in plain text... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 25, 2006 8:59 AM To: dev@httpd.apache.org Subject: RE: Ignore all filters except ssl one I amm bound to use Apache as it is acting as reverse proxy and I have to make this tunnel through it only. -Original Message- From: Joost de Heer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 18, 2006 10:26 PM To: dev@httpd.apache.org Subject: Re: Ignore all filters except ssl one [EMAIL PROTECTED] wrote: > Hi, > I need to create a tunnel between client and backend server through > Apache just like CONNECT call does but cant turn forward proxying. Are you bound by using Apache? If not, might I suggest rinetd (http://www.boutell.com/rinetd/) for this purpose? It's really easy to configure, and does exactly what you want to do. Joost The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.
RE: Ignore all filters except ssl one
Title: RE: Ignore all filters except ssl one I amm bound to use Apache as it is acting as reverse proxy and I have to make this tunnel through it only. -Original Message- From: Joost de Heer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 18, 2006 10:26 PM To: dev@httpd.apache.org Subject: Re: Ignore all filters except ssl one [EMAIL PROTECTED] wrote: > Hi, > I need to create a tunnel between client and backend server through > Apache just like CONNECT call does but cant turn forward proxying. Are you bound by using Apache? If not, might I suggest rinetd (http://www.boutell.com/rinetd/) for this purpose? It's really easy to configure, and does exactly what you want to do. Joost
Re: Ignore all filters except ssl one
[EMAIL PROTECTED] wrote: Hi, I need to create a tunnel between client and backend server through Apache just like CONNECT call does but cant turn forward proxying. Are you bound by using Apache? If not, might I suggest rinetd (http://www.boutell.com/rinetd/) for this purpose? It's really easy to configure, and does exactly what you want to do. Joost
Ignore all filters except ssl one
Title: Ignore all filters except ssl one Hi, I need to create a tunnel between client and backend server through Apache just like CONNECT call does but cant turn forward proxying. I have copied the code for CONNECT logic in my function. The client is communicating with apache on SSL and apache communicates with backend server in plain text. The tunnel works fine for simple web sites. It does not work when I try to tunnel pop3 or smtp through it. I am using a wrapper application on client and backend server which uses chunked encoded http messages to create pop3/smtp tunnel. Its working fine for small messages. For attachments, Apache suddenly sends tcp reset to client side and disconnects both ends. Please suggest changes, satti
