RE: [PATCH] WAP access-log logging 502 (Bad Gateway) for HTTP requests failing

I have applied the patch, tested for 3 cases
1. DNS can not resolve host name
2. Page accessed gives 500 error
3. gw can not connect to the http server
All error are logged in wap-access.log, no problem with gateway.
Now this version of gw is running on my production server.

So +1 to commit to cvs from me.

> -----Original Message-----
> From: Stipe Tolj [mailto:[email protected]]
> Sent: Monday, December 15, 2003 3:26 PM
> To: Kannel Devel
> Subject: [PATCH] WAP access-log logging 502 (Bad Gateway) for 
> HTTP requests failing
> 
> 
> Hi list,
> 
> here is a patch that will allow to log 502 HTTP response code for
> proxied WAP GW requests that did not have any internal HTTP response
> code, ie. wapbox could not connect to the port or host was not
> reachable.
> 
> Please try and vote on commitment.
> 
> Stipe
> 
> mailto:[email protected]
> -------------------------------------------------------------------
> Wapme Systems AG
> 
> Münsterstr. 248
> 40470 Düsseldorf, NRW, Germany
> 
> phone: +49.211.74845.0
> fax: +49.211.74845.299
> 
> mailto:[email protected]
> http://www.wapme-systems.de/
> -------------------------------------------------------------------
> 
> -----BEGIN PGP PUBLIC KEY BLOCK-----
> Version: GnuPG v1.2.2 (Cygwin)
> 
> mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
> OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
> nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
> dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
> bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
> AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
> OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
> K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
> g2HyLAEKQIp30Q==
> =aYCI
> -----END PGP PUBLIC KEY BLOCK-----
>