Try removing the HeadRequire...  That's my guess.
-- 
Joe

Confidentiality Notice: This e-mail transmission may contain confidential and 
legally privileged information that is intended only for the individual named 
in the e-mail address. If you are not the intended recipient, you are hereby 
notified that any disclosure, copying, distribution, or reliance upon the 
contents of this e-mail message is strictly prohibited. If you have received 
this e-mail transmission in error, please reply to the sender, so that proper 
delivery can be arranged, and please delete the message from your mail box.






On 6/30/15, 11:32 PM, "Ross Draper" <[email protected]> wrote:

>Hi All
>
>I¹m running pound 2.6 on ubuntu 12.04.
>
>I¹ve just run into an issue whereby a client application that is doing
>HTTP POST requests to a back end server is failing and generating the
>following:
>
>pound: (7f223691e700) e503 no service "POST /api/getAmount HTTP/1.1" from
>10.16.10.15 127.0.0.1:18443
>
>If I perform a GET, the service is fine and I get the desired response and
>a 200 from Pound in the logs. The xHTTP parameter seems correct and I have
>even tried changing it, but with no luck.
>
>Can anybody suggest any troubleshooting steps?  This is a new service -
>not something that suddenly went bad.
>
>ListenHTTPS
>        Address xxx.xxx.xxx.xxx
>        Port    8443
>       xHTTP   4
>cert    "/etc/ssl/private/cert1.pem"
>       cert    "/etc/ssl/private/cert2.pem"
>       ClientCert 2 8
>       VerifyList "/etc/ssl/private/cacert.pem"
>       RewriteLocation 2
>       SSLHonorCipherOrder 1
>       Ciphers "ALL:!ADH:RC4+RSA:+HIGH:!MEDIUM:!LOW:!SSLv2:!EXPORT"
>       AddHeader "X-Forwarded-SSL: on"
>        AddHeader "X-Forwarded-Proto: https"
>end
>
>
>
>Service
>        HeadRequire "Host: (my_host_name)"
>        DynScale        1
>        BackEnd
>                Address xxxxx
>Port xxxx
>        End
>End
>
>
>Many thanks
>
>Ross
>
>
>--
>To unsubscribe send an email with subject unsubscribe to [email protected].
>Please contact [email protected] for questions.

Reply via email to