Sponsored Content
Top Forums Shell Programming and Scripting SIMPLE HTTP PROXY SERVER CHECKER (Completed) Post 302651125 by 654321 on Tuesday 5th of June 2012 03:05:22 AM
Old 06-05-2012
MySQL

I found that some proxies work different with cookies
That is why I added second check for Elite proxy servers.

... Now I found that some proxies work different with header "Cache-Control: no-cache" . That is why I added such header in second check.

Last edited by 654321; 11-15-2012 at 03:56 AM..
These 2 Users Gave Thanks to 654321 For This Post:
 

8 More Discussions You Might Find Interesting

1. Programming

Proxy Checker in C

Hello Everyone Im planning to make a C program to check a proxy server if it is working or bot, test the proxy speed ,response time , as well as a proxy type. i'm learning using libcurl right now to fetch http headers. do you guys have some links about how to check proxy headers?. Thank you. ... (0 Replies)
Discussion started by: magictalong
0 Replies

2. Programming

Tools for writing a simple syntax checker?

I'm trying to write a small utility for syntax checking. I've tried using Flex/Bison, but these seem too advanced for my task. A simpler tool would be appreciated. (1 Reply)
Discussion started by: Ilja
1 Replies

3. IP Networking

Software/tool to route an IP packet to proxy server and capture the Proxy reply as an

Hi, I am involved in a project on Debian. One of my requirement is to route an IP packet in my application to a proxy server and receive the reply from the proxy server as an IP packet. My application handles data at the IP frame level. My application creates an IP packet(with all the necessary... (0 Replies)
Discussion started by: Rajesh_BK
0 Replies

4. Shell Programming and Scripting

Simple HTTP server in GAWK

Hi, Not sure if this post belongs to this forum but I have been trying every so often to setup a simple http server in awk. After a couple of try and errors I finally came across this: REMCONF - TCP/IP Internetworking With `gawk' This tutorial is not to cut and paste without change, so here... (0 Replies)
Discussion started by: ripat
0 Replies

5. Programming

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: GET / HTTP/1.0 Host: http://www.google.com Connection:... (0 Replies)
Discussion started by: shubham92
0 Replies

6. Shell Programming and Scripting

Completed: Domain name tools. Generator & Checker

I'm fairly new to bash scripts, and all things unix in general. But I was in desperate need of this script, so I took matters into my own hands and built it! The first script uses a password generator that creates 4 letter domain names and outputs only the ones that are available. Currently its... (0 Replies)
Discussion started by: Files
0 Replies

7. Web Development

Http connect to proxy to websockets

I am having a hard time with this one. We have a websocket server listening on port 80 at myserver.com/wsDemo?ID=12. We need to test a client program by connecting it to this server through a proxy. I am trying nginx 1.2.7 as the proxy on port 8080, running on proxy-server. We want the client to... (1 Reply)
Discussion started by: glev2005
1 Replies

8. AIX

Configure HTTP proxy in SUMA

Hi, I am trying to configure an HTTP_PROXY so that suma can reach out beyond our intranet and pull updates from the IBM website. Currently, our suma config is the default as it's not been used before. When I attempt to issue the following command sudo suma... (7 Replies)
Discussion started by: JAR1
7 Replies
PROXYMNGR(1)						      General Commands Manual						      PROXYMNGR(1)

NAME
proxymngr - proxy manager service SYNOPSIS
proxymngr [-config filename] [-timeout seconds] [-retries #] [-verbose] DESCRIPTION
The proxy manager (proxymngr) is responsible for resolving requests from xfindproxy (and other similar clients), starting new proxies when appropriate, and keeping track of all of the available proxy services. The proxy manager strives to reuse existing proxies whenever possi- ble. There are two types of proxies that the proxy manager deals with, managed and unmanaged proxies. A managed proxy is a proxy that is started ``on demand'' by the proxy manager. An unmanaged proxy, on the other hand, is started either at system boot time, or manually by a system administrator. The proxy manager is made aware of its existence, but no attempt is made by the proxy manager to start unmanaged proxies. The command line options that can be specified to proxymngr are: -config Used to override the default proxymngr config file. See below for more details about the config file. -timeout Sets the number of seconds between attempts made by the proxy manager to find an unmanaged proxy. The default is 10. -retries Sets the maximum number of retries made by the proxy manager to find an an unmanaged proxy. The default is 3. -verbose Causes various debugging and tracing records to be displayed as requests are received and proxies are started. Proxy Manager Config File The proxy manager maintains a local configuration file describing the proxy services available. This configuration file is installed in /usr/X11R6/lib/X11/proxymngr/pmconfig during the installation of proxymngr. The location of the configuration file can be overwritten using the -config command line option. Aside from lines starting with an exclamation point for comments, each line of the configuration file describes either an unmanaged or man- aged proxy service. For unmanaged proxies, the format is: <service-name> unmanaged <proxy-address> service-name is the name of the unmanaged proxy service, and must not contain any spaces, for example ``XFWP''. service-name is case insenstive. proxy-address is the network address of the unmanaged proxy. The format of the address is specific to the service-name. For example, for the ``XFWP'' service, the proxy-address might be ``firewall.x.org:100''. If there is more than one entry in the config file with the same unmanaged service-name, the proxy manager will try to use the proxies in the order presented in the config file. For managed proxies, the format is: <service-name> managed <command-to-start-proxy> service-name is the name of the managed proxy service, and must not contain any spaces, for example ``LBX''. service-name is case insensi- tive. command-to-start-proxy is the command executed by the proxy manager to start a new instance of the proxy. If command-to-start-proxy con- tains spaces, the complete command should be surrounded by single quotes. If desired, command-to-start-proxy can be used to start a proxy on a remote machine. The specifics of the remote execution method used to do this is not specified here. EXAMPLE
Here is a sample configuration file: ! proxy manager config file ! ! Each line has the format: ! <serviceName> managed <startCommand> ! or ! <serviceName> unmanaged <proxyAddress> ! lbx managed /usr/X11R6/bin/lbxproxy ! ! substitute site-specific info xfwp unmanaged firewall:4444 PROXY MANAGER DETAILS
When the proxy manager gets a request from xfindproxy (or another similar client), its course of action will depend on the service-name in question. For a managed proxy service, the proxy manager will find out if any of the already running proxies for this service can handle a new request. If not, the proxy manager will attempt to start up a new instance of the proxy (using the command-to-start-proxy found in the config file). If that fails, an error will be returned to the caller. For an unmanaged proxy service, the proxy manager will look in the config file to find all unmanaged proxies for this service. If there is more than one entry in the config file with the same unmanaged service-name, the proxy manager will try to use the proxies in the order presented in the config file. If none of the unmanged proxies can satisfy the request, the proxy manager will timeout for a configurable amount of time (specified by -timeout or default of 10) and reattempt to find an unmanaged proxy willing to satisfy the request. The num- ber of retries can be specified by the -retries argument, or a default of 3 will be used. If the retries fail, the proxy manager has no choice but to return an error to the caller (since the proxy manager can not start unmanaged proxy services). BUGS
proxy manager listen port should be configurable. -timeout and -retries is not implemented in proxymngr. proxymngr does not utilize the ``options'' and ``host'' fields in the proxy management protocol GetProxyAddr request. SEE ALSO
xfindproxy (1), xfwp (1), Proxy Management Protocol spec V1.0 AUTHOR
Ralph Mor, X Consortium X Version 11 Release 6.6 PROXYMNGR(1)
All times are GMT -4. The time now is 08:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy