Sorry, I meant red hat with Oracle. (Oracle has it's own Apache server, and
the default for ssl is port 443.) 

-----Original Message-----
From: Simon Matter [mailto:[email protected]] 
Sent: Friday, April 02, 2010 2:38 PM
To: [email protected]
Subject: RE: [Pound Mailing List] Help - Pound not redirecting to backend
servers

> Hi Jake
>
> On Linux (red hat), the SSL port (by default) is normally on port 
> 4443, (not 443).

Huh, how comes? I have never seen that in my life and I'm a RedHat user for
more than a decade. Are we talking about the same, running apache with SSL?

Regards,
Simon

>
> Thanks
>
> Anne
>
> -----Original Message-----
> From: Jacob Anderson [mailto:[email protected]]
> Sent: Friday, April 02, 2010 1:46 PM
> To: [email protected]
> Subject: RE: [Pound Mailing List] Help - Pound not redirecting to 
> backend servers
>
> Hi Anne,
>
> SSL is always on port 443 unless you explicitly reset that port number 
> to be 4443. If you are using a default configuration for your back end 
> servers, then change your pound config to proxy back to port 443 on 
> your back end servers.
>
> -- Jake
>
>
> -----Original Message-----
> From: Anne Moore [mailto:[email protected]]
> Sent: Friday, April 02, 2010 10:29 AM
> To: [email protected]
> Subject: RE: [Pound Mailing List] Help - Pound not redirecting to 
> backend servers
>
> I removed the lines "Port 4443" and now I get this error:
>
> "The service is not available. Please try again later."
>
> So, now I'm really stuck.
>
> Is there any way to proxy to an SSL backend (on linux, so it's port 
> 4443), like this? (https://TTRH2.helpme.org:4443/myapp) ?
>
> Thanks
>
>
> -----Original Message-----
> From: Anne Moore [mailto:[email protected]]
> Sent: Friday, April 02, 2010 1:20 PM
> To: '[email protected]'
> Subject: RE: [Pound Mailing List] Help - Pound not redirecting to 
> backend servers
>
> Hi Zs
>
> Unfortunately, that didn't work. I get this error message when trying 
> to start pound:
>
> "/usr/local/etc/pound.cfg line 31: Port is supported only for 
> INET/INET6 back-ends"
>
> So it looks like it's saying port 4443 is not supported with pound?
>
> What do you think?
>
> Thanks
>
> Anne
>
>
> -----Original Message-----
> From: Zack Steinkamp [mailto:[email protected]]
> Sent: Friday, April 02, 2010 12:06 PM
> To: [email protected]
> Subject: Re: [Pound Mailing List] Help - Pound not redirecting to 
> backend servers
>
> Put the Service blocks inside the ListenHTTP block.
>
> -zs
>
>
> On 4/2/10 8:39 AM, Anne Moore wrote:
>> All,
>>
>> I just can't seem to get my pound working. (Please see my pound.cfg
> below).
>> When my users to go the "172.29.1.22" server, they receive this error
>> message: "The service is not available. Please try again later."
>>
>> As you can see from my pound.cfg, it's supposed to redirect it to a 
>> url at one of the two backend servers (which are Linux and have port
>> 4443 for SSL.)
>>
>>
>> Any idea what I'm doing wrong here?
>>
>> Thank you for any help you're willing to provide.
>>
>> Anne
>>
>> ######################################################
>> ListenHTTP
>>      Address 172.29.1.222
>>      Port    80
>>      xHTTP   1
>>      HeadRemove "X-SSL-Request"
>>      HeadRemove "X-Forwarded-For"
>>      AddHeader  "X-SSL-Request: 1"
>> End
>>
>> # redirect all requests for /forbidden
>>
>> Service
>>    Url         "<http://TTHR3.helpme.org>  http://TTHR3.helpme.org";
>>    Redirect    "<https://TTHR3.helpme.org/myapp>
>> https://TTHR3.helpme.org/myapp";
>> End
>>
>> # Catch-all server(s)
>> Service
>>      BackEnd
>>          Address<https://TTRH1.helpme.org:4443:/myapp>
>> https://TTRH1.helpme.org:4443:/myapp
>>          Port 4443
>>      End
>>      BackEnd
>>          Address<https://TTRH2.helpme.org:4443/myapp>
>> https://TTRH2.helpme.org:4443/myapp
>>          Port 4443
>>    End
>>   Session
>>          Type    IP
>>          TTL     520
>>      End
>> End
>> ###############################################################
>>
>>
>> --
>> 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.
>
>
> --
> 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.
>
>
> --
> 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.


--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

Reply via email to