On 12/16/03(00:01) you "Lepczynski, Bernd" <pxueqbdyi-mxhgu4y6n2xw.ml@delegate.org> wrote in <_A2503@delegate-en.ML_> |Thanks for that hint you gave me before. | |Now RPC seems to be working , but another http error: | |----------------------snip----------------------------------------- ... |12/15 15:47:11.04 [1296] 2+1: #HT11 resp version: HTTP/1.0 -> 1.1 |12/15 15:47:11.04 [1296] 2+1: HTTP error request: RPC_IN_DATA |/rpc/rpcproxy.dll?hts9340.HDW9.HDWGroup9.net:6002 HTTP/1.1^M |12/15 15:47:11.06 [1296] 2+1: HTTP error status: 503 RPC Error: 6BA ... |We had checked the staus error 503. This means that the process is closed |because of an Error in header. As long as I know, the error code 503 means that the server is not available. [RFC2616 HTTP/1.1] > >10.5.4 503 Service Unavailable > > The server is currently unable to handle the request due to a > temporary overloading or maintenance of the server. The implication > is that this is a temporary condition which will be alleviated after > some delay. If known, the length of the delay MAY be indicated in a > Retry-After header. If no Retry-After is given, the client SHOULD > handle the response as it would for a 500 response. > > Note: The existence of the 503 status code does not imply that a > server must use it when becoming overloaded. Some servers may wish > to simply refuse the connection. Possibly it means that your RPC/HTTP gateway is not working by some reason. The error log of the RPC/HTTP server, if exists, might show what is wrong. |Do you have a big hint again ?? I don't understand why you use two DeleGates just to relay HTTPS to HTTPS. It can be done simply, without concering with SSL nor HTTP, like this: delegated -P443 SERVER=tcprelay://rpc-over-https-server:443 ADMIN=xxx Cheers, Yutaka -- D G Yutaka Sato <y.sato@delegate.org> http://www.delegate.org/y.sato/ ( - ) National Institute of Advanced Industrial Science and Technology (AIST) _< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan Do the more with the less -- B. Fuller
V