Sending and Receiving data between Client, HTTP Proxy, and Remote Server
I am having problems receiving data from a remote server. It seems that I can send an HTTP request to any host such as http://www.google.com, but I can't get a reply.
I'm sending the host a HTTP 1.0 request that is formatted as such:
hi dear i m very new to socket programing .
i need the source code which sends file from server to client .
i mean both server n client programe which sends file .
can u do this for me please
my email id is email id removed
regards bilal (1 Reply)
I have been toying with a Proxy client/server app that will listen on the CLIENT system on lets say port 7070. User's browser proxy setting is configured for "localhost" port "7070".
When this proxy app gets a request for a URL it should FETCH the URL and display it on the browser.
I... (1 Reply)
Hi,
Not sure if this is possible, I have a server (SERVER1) that is currently set up as a remote SSH host. My client SSH host (SERVER2) is connecting to SERVER1 to scp a file with no password.
I now have a need to set up a third server (SERVER3) as a remote SSH host and I need SERVER1 as a... (4 Replies)
I'm looking for a couple high level pointers to writing a UDP server that will be acknowledging data at a rate of approximately twelve packets every second and will be running on and older but more or less dedicated Solaris 9 box.
Acknowledging the data packets is relatively simple, after... (2 Replies)
Hi I have managed to connect to a remote server via ssh, but nothing will actually send through to the remote server screen through my script...it waits until i am back to the main terminal before it outputs anything.
Can anyone tell me how to get commands to send through to the remote server?... (4 Replies)
hi
am senthil
am developing a software to send and receive SMS using HTTP connection
first of all am forming a URL and sending that URL to a remote server using my Client Program
i send that url through Socket(using Send() Function)
if i send more than one URL one by one using the same... (0 Replies)
hi
am senthil
am developing a software to send and receive SMS using HTTP connection
first of all am forming a URL and sending that URL to a remote server using my Client Program
i send that url through Socket(using Send() Function)
if i send more than one URL one by one using the same... (4 Replies)
Simple Http Proxy Server Checker Script with curl
mirror proxies-scripts/proxc at master * Anoncheg1/proxies-scripts * GitHub
output in terminal
HTTP, HTTP Connect (HTTPS not supported)
command line:
proxc filename
where filename is file like
119.110.69.185:8080
119.235.16.41:8080... (4 Replies)
I need to do some remote administration to an access point that is sitting behind a firewall that only has ssh enable from the outside but http/https from the inside. So to be a bit clearer:
remote(outside firewall) ssh --> ssh-server(internal) --> access point(http/https)
Ultimately... (3 Replies)
Discussion started by: metallica1973
3 Replies
LEARN ABOUT SUSE
xmlrpc::transport::http
XMLRPC::Transport::HTTP(3) User Contributed Perl Documentation XMLRPC::Transport::HTTP(3)NAME
XMLRPC::Transport::HTTP - Server/Client side HTTP support for XMLRPC::Lite
SYNOPSIS
Client
use XMLRPC::Lite
proxy => 'http://localhost/',
# proxy => 'http://localhost/cgi-bin/xmlrpc.cgi', # local CGI server
# proxy => 'http://localhost/', # local daemon server
# proxy => 'http://login:password@localhost/cgi-bin/xmlrpc.cgi', # local CGI server with authentication
;
print getStateName(1);
CGI server
use XMLRPC::Transport::HTTP;
my $server = XMLRPC::Transport::HTTP::CGI
-> dispatch_to('methodName')
-> handle
;
Daemon server
use XMLRPC::Transport::HTTP;
my $daemon = XMLRPC::Transport::HTTP::Daemon
-> new (LocalPort => 80)
-> dispatch_to('methodName')
;
print "Contact to XMLRPC server at ", $daemon->url, "
";
$daemon->handle;
DESCRIPTION
This class encapsulates all HTTP related logic for a XMLRPC server, independent of what web server it's attached to. If you want to use
this class you should follow simple guideline mentioned above.
PROXY SETTINGS
You can use any proxy setting you use with LWP::UserAgent modules:
XMLRPC::Lite->proxy('http://endpoint.server/',
proxy => ['http' => 'http://my.proxy.server']);
or
$xmlrpc->transport->proxy('http' => 'http://my.proxy.server');
should specify proxy server for you. And if you use "HTTP_proxy_user" and "HTTP_proxy_pass" for proxy authorization SOAP::Lite should know
how to handle it properly.
COOKIE-BASED AUTHENTICATION
use HTTP::Cookies;
my $cookies = HTTP::Cookies->new(ignore_discard => 1);
# you may also add 'file' if you want to keep them between sessions
my $xmlrpc = XMLRPC::Lite->proxy('http://localhost/');
$xmlrpc->transport->cookie_jar($cookies);
Cookies will be taken from response and provided for request. You may always add another cookie (or extract what you need after response)
with HTTP::Cookies interface.
You may also do it in one line:
$xmlrpc->proxy('http://localhost/',
cookie_jar => HTTP::Cookies->new(ignore_discard => 1));
COMPRESSION
XMLRPC::Lite provides you option for enabling compression on wire (for HTTP transport only). Both server and client should support this
capability, but this logic should be absolutely transparent for your application. Server will respond with encoded message only if client
can accept it (client sends Accept-Encoding with 'deflate' or '*' values) and client has fallback logic, so if server doesn't understand
specified encoding (Content-Encoding: deflate) and returns proper error code (415 NOT ACCEPTABLE) client will repeat the same request not
encoded and will store this server in per-session cache, so all other requests will go there without encoding.
Having options on client and server side that let you specify threshold for compression you can safely enable this feature on both client
and server side.
Compression will be enabled on client side IF: threshold is specified AND size of current message is bigger than threshold AND module
Compress::Zlib is available. Client will send header 'Accept-Encoding' with value 'deflate' if threshold is specified AND module
Compress::Zlib is available.
Server will accept compressed message if module Compress::Zlib is available, and will respond with compressed message ONLY IF: threshold is
specified AND size of current message is bigger than threshold AND module Compress::Zlib is available AND header 'Accept-Encoding' is
presented in request.
DEPENDENCIES
Crypt::SSLeay for HTTPS/SSL
HTTP::Daemon for XMLRPC::Transport::HTTP::Daemon
Apache, Apache::Constants for XMLRPC::Transport::HTTP::Apache
SEE ALSO
See ::CGI, ::Daemon and ::Apache for implementation details.
See examples/XMLRPC/* for examples.
COPYRIGHT
Copyright (C) 2000-2001 Paul Kulchenko. All rights reserved.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
AUTHOR
Paul Kulchenko (paulclinger@yahoo.com)
perl v5.12.1 2010-03-18 XMLRPC::Transport::HTTP(3)