If you do not want to use MS IE using HTTP Proxy interface but using SOCKS, delete in the dialog Proxy settings the entry in line HTTP and replace it with entry in SOCKS line. As the port number use 1080 or another if you have also changed the default settings of Proxy+.

If you do not want to use NN using HTTP Proxy interface but using SOCKS, delete in the dialog Manual Proxy Configuration the entry in the line HTTP: and replace it with the entry in the line SOCKS. As the port number use 1080 or another if you have also changed the default settings of Proxy+.

If there is a configuration of proxy servers in the SOCKS settings, the program Messenger (post client) uses the protocol SOCKS to read and send mails and to read News. You can use it with advantage for the simpler access to News Servers - you do not have to use mapped links.

Generally there are three options how to connect to Internet:

• Dial-up
• Asynchronous dedicated line
• Synchronous dedicated line

4.2.1 Dial-up

The most common option. The connection is realized using modem and ordinary telephone line. It is mandatory to connect first (to dial a phone number). Proxy+ supports user defined (manual) and automatic dial-ups / hang-ups.

4.2.2 Asynchronous dedicated line

A connection realized via leased line with asynchronous modems on both sides. The connected PC is connected permanently to the Internet.
In Windows there is not a good support for this type of connection - if a connection is lost, it is not automatically reconnected or restored. Therefore Proxy+ has some features implemented to correct the imperfections of this kind of connection in Windows.

The connection via asynchronous dedicated line is generally realized with the installation of the driver NULL modem which is used for the formation and configuration of the dial-up. The modems are configured to connect automatically without manual interference. Herewith the condition to support the physical connection is complete but it is necessary to connect in the logic layer (PPP protocol). That is done only using the activation of the dial-up connection.

4.2.3 Synchronous dedicated line

4.2.4 Configuration of a dial-up

First you have to create a new configuration of a telephone connection to your ISP. You can use the icon "My computer/Telephone connection/New connection" (in Windows NT only "My computer/Telephone connection"). You should get the parameters needed from your ISP.

Notice: Proxy+ registers each access to its services (doesn't apply to admin. interface and postal services) and after the specified action is finished, it keeps the user as inactive in the list for one more minute. During this time it doesn't hang up automatically. If you set the automatic hang up after 0 minutes, then the hang up takes place one minute after the user has finished to read pages from WWW server. This delay is necessary because otherwise the Proxy+ would have to dial up too often.

If an automatic connection was established to process mails the hang up is executed with no delay after all outgoing mails are sent and all incoming mails are received. But if there would be another service running during the postal process Proxy+ hangs up after the set delay.

Automatic dial-up
Proxy+ supports the automatic dial up connection at the beginning of the request to read or send data. On the page Dialing/Auto Dial you can specify what services are enabled to use automatic dialing. The first line can enable/disable AutoDial-up in global.

Proxy+ supports two modes for automatic dial-ups. Either it can dial without any further controls when no active connection to Internet is available (AutoDial if disconnected) or it will first try whether the requested server is not available without establishing a dial-up connection (for local server, Intranet WWW server) and only if it cannot reach the requested data it will dial up a telephone connection. You may choose between those two modes on the page Dialing/Auto Dial Extended.

AutoDial if disconnected
Advantage of this mode is that the reaction of proxy server is immediate - instantly after the request proxy will dial up. But if the request would be directed into local server, the dial-up would be unnecessary.
This mode is implicit.

AutoDial if unreachable
This mode's advantage is that it dials only in the case that it really is impossible to contact the requested target server without the dial-up. The disadvantage is that sometimes the determination of inaccessibility of the server may last quite a long time - tens of seconds to few minutes.

Because the servers with interesting data are mostly in Internet (a dial-up is required) it is better to choose the automatic dial up (if disconnected). If there is an intranet WWW server in the local net, you can configure your browsers in LAN using the exceptions not to use proxy servers accessing this server.

It is also good to configure Proxy+ to ignore dial-up requests when you enter into URL with disabled AutoDial the IP addresses and the name of local servers. The addresses are entered in URL mode.

Examples of disabled dial-ups:

Using alternative phone numbers
If your ISP has more different phone numbers, you can take the advantage of Proxy+ feature to change the phone numbers when connecting. If there is a busy line on one connection, the second may be free. Because Proxy+ attempts to connect to Internet for many times, then when the line is busy, it automatically switches onto the other.

To use alternative numbers set on page Dialing/Extended the option Use alternate phone numbers and fill in the list of phone numbers to the edit line Alternate phone numbers. Numbers are separated with a colon or a semicolon.

If the use of alternative phone numbers is off (default value), Proxy+ doesn't specify the phone number and the Windows system uses the number filled in its telephone connection.

Proxy+ supports to define alternative delay (shorter or longer than the standard one) and also the time schedule when the alternative delay should be used.
On page Dialing/Extended check Use alternate Hang up timeout and fill in the requested delay in minutes. In the check box field Alternate Hang up timeout is enabled in these hours fill in the hours in specific days of the week when alternative delay should be used.

4.2.5 Configuration of a asynchronous dedicated line

Configuration of Proxy+ to work with asynchronous dedicated line (ADL)
The settings for ADL is similar to "common" dial-up. The only difference is that the option Async Leased Line must be checked.
In the ADL mode Proxy+ automatically connect on the program start-up and it doesn't hang up automatically. But you are able to hang up the line manually from the admin. interface.

If there is no authentication needed on your ADL (name and password) fill in the lines User name and User password any characters (it shouldn't remain empty).

Notice: The configuration of the automatic hang up is ignored in this mode.

Because Windows do not have a support for this type of connection, it is necessary to configure Proxy+ to connect immediately when the connection is lost. It is necessary to enable the automatic dial-up from all used services and protocols. Herewith you secure that any request of data reading from Internet will automatically re-establish the connection.
You can also use Proxy+ mail server to re-establish the lost connection. Configure it to check whether there is a mail on your ISP POP3 server every 10 minutes. Enable the automatic dial-up from all mail actions and enable all hours in all days during the week on page Mail/Valid time intervals.

4.2.6 Configuration of synchronous dedicated line

4.3 Demonstration of a post system settings

On the page Mail/POP3 Download set:

You can leave other options in their default values unless you want to configure Proxy+ to leave messages on the server or to use POP3 restrictions for example.

And then press the Add button. A new entry is added to the POP3 users list.

4.3.3 Setting of the reading of messages from POP3 box using the sorting rulesets

The sorting of the messages read from POP3 server is usually used if:
- it is a mail box of the "domain" mail - mail server stores messages for the whole domain into a single mailbox.
- messages directed to more email addresses is stored to a single mailbox (primary address has more aliases).

On the page Mail/POP3 Download set:

You can leave other options in their default values unless you want to configure Proxy+ to leave messages on the server or to use POP3 restrictions for example.

And then press the Add button. A new entry is added to the POP3 users list.

When reading new messages, each message is going through the procedure, that delivers the message to the local users according to the sorting ruleset sorting.

4.3.4 Basic demonstration of a ruleset (domain box)

Example: The company uses for incoming messages a domain box, that means it has a registered domain and the ISP's mail server stores all incoming messages into one single mailbox. We want to configure the sorting rulesets to sort the messages according to the content of the header field "To:".

Further, if no matching rule is found, we want user marlowe to receive the message.

On page Mail/Sorting Rules create new sorting ruleset. Enter the name (e.g. sorting) to New ruleset name and press Add button. In Defined rules choose the new rule and press Edit.

On a new page we define the characteristics in this way:
Default user: - the implicit user is marlowe. So please choose his name from the list.
Carbon copy user: - you can choose a user who will get a copy of each message that goes through the sorting rules.
User defined head: - serves to define the sorting according to the non-standard header.
Append to rule: - because all processed email addresses end with the same text @company.com, we can enter this text into this line. Then the search string will not look for jsmith, but for jsmith@company.com.
Note: sometimes it would be fine if the content of the Append to: item is not appended to the rule keyword. In the case add '~' character to the end of the keyword. Example: jsmith@anothercompany.com.

1) Settings for the user smith1:

2) Settings for the user smith2 :

3) Settings for the user marlowe:

User: - choose the user [administration].
To: - enter the text: company

Press Add button. In the list Defined rules the entry [administration] < OR;To:company appears.

Example: The company uses for incoming messages one mailbox only. There is no domain post nor aliases defined. The e-mail address of the box is company@server.com. We want to configure the sorting rules to sort the messages according to the content of the header "To:".

Example:
John Smith <jsmith@server.com>
"Joseph Smith" <jsmith@server.com>

Let's say we want to sort the post for Peter and John. User john is the default user of the sorting ruleset. We assume that John's messages will contain the search string "john" in the header "To:" and Peter's the string "peter".

Create a new sorting ruleset on page Mail/Sorting Rules. Enter a new name (e.g. sorting) to New ruleset name and press Add. In Defined rules choose a new rule and press Edit.

On a new page we define the characteristics in this way:
Default user: - we have chosen as the default user the user john. So we choose his name from the list.
Carbon copy user: - if you choose a user he will get a copy of each message that goes through the sorting rules.
User defined head: - serves to define the sorting according to the non-standard header. We do not use it in our case
Append to rule: - We have to leave this line inactive because we do not sort according to the email address but according to the plain text in the entry "To:" only. Or we have to append '~' character to rule keyword.

User: - choose user john.
To: - enter the text: john. We can use john~ too (to disable the Append to feature for the keyword).

User: - choose user peter.
To: - enter the text: peter. We can use peter~ too (to disable the Append to feature for the keyword).

We can also define this ruleset easier. If we say that John should get all messages excluding those containing the search string "peter" , it is obvious that for a correct sorting it is enough to let john be the default user and to declare the sorting rule for user peter only. So we can pass the step 1) in the above text.

1) Using the mailing system of Proxy+
Proxy+ reads the content of POP3 box in Internet, saves it to local disk and the mailing programs collect the messages from Proxy+. The outgoing messages are sent first to Proxy+ and it sends them away according to defined specifications further to Internet. From the view of the mail client Proxy+ behaves as a complete SMTP and POP3 mail server.

TCP 4425 mail.server.com:25
TCP 44110 mail.server:110

If you enable the automatic dial-up for Mapped Links the mail client has the possibility with a simple request (to send or to receive mails) to open up a connection.

POP3 Mapped Links
Proxy+ supports special mapped connection for POP3 protocol - POP3 Mapped link. Proxy+ is able to determine name of POP3 server from the request and then use only one mapped connection for reading mail from more than one POP3 servers. To make POP3 Mapped Links works correctly, mail client must be configured to send name of mailbox in following format: mailbox_name#POP3_server_name. So it's necessary to modify POP3 account setting, all other settings are the same as above.

3) Direct access to SMTP and POP3 server using SOCKS.
If the mail client supports SOCKS protocol and you want for any reason to let it access to mail servers in Internet directly this mode is simpler and lucid than Mapped Links.

Outlook Express - connecting to mailing system of Proxy+

Example: On the PC running Proxy+ we have defined an account of the user test with password 12345. Mailing system of Proxy+ is correctly configured and reads the mailbox from Internet and stores it into the box of the test user. We want Outlook Express on the local LAN station to receive the content of the box of this user.
Proxy+ runs on a PC with the IP address 192.168.0.1

Definition of a new account:
Through menu Tools/Accounts ask for the form Internet Accounts. Press Add button and choose the option Mail from the list given. A wizard guiding you through the new account creation will start. Fill in or check these entries:

• Name that will be stored as a part of outgoing mails you send.
• Your email address.
• Type of incoming mail server: POP3
• Incoming mail (POP3) server: 192.168.0.1
• Outgoing mail (SMTP) server: 192.168.0.1
• Logon using
• POP account name: test
• Password: 12345
• Internet mail account name: enter the name under which the new account will be shown in the list of accounts.
• Connect using my local area network. Important, otherwise Outlook Express will activate telephone connection.

Changing already existing account:
In Tools/Accounts ask for the Internet Accounts. Choose the required account from the list and press the button Properties. In the shown form change these entries:

in the marker Servers: 

• Incoming mail (POP3) server: 192.168.0.1
• Outgoing mail (SMTP) server: 192.168.0.1
• Logon using
• Account name: test
• Password: 12345

in the marker Connection: 

• Connect using my local area network (LAN)

Notice: If the account has been created with a different type of server for incoming mail than POP3 (IMAP) you have to delete this account and create a new one.

Netscape Messenger 4.5 - connecting to the mailing system of Proxy+

Example: On the PC running Proxy+ we have defined an account of the user test with password 12345. Mailing system of Proxy+ is correctly configured and reads the mailbox from Internet and stores it into the box of the test user. We want Netscape Messenger on the local station in LAN to receive the content of the box of this user.
Proxy+ runs on a PC with the IP address 192.168.0.1

• "I'm using a permanent connection to LAN" and "I'm behind a firewall or proxy"
• Press the "Firewall Settings" button and set "I am using a SOCKS5 Proxy server"
• Press "Next" button and enter the IP address of the PC running Proxy+ in the line "SOCKS5 host". To "SOCKS5 port" enter number 1080 (or other you set up in the settings of SOCKS protocol in Proxy+).
  If you are using ICQ 99a or newer enable the option Resolve IP.
  If you use Proxy+ version older than 2.10 make sure that the option "Use RFC1929 authentication for SOCKS" is disabled. Newer versions of Proxy+ already support the authentication of the user.
• Finish with pressing the "Next" button. In the next dialog window you are advised to test the connection through Proxy+. If your Proxy+ is already connected to Internet, use the button "Check My FIREWALL / Proxy Settings" to test, if the settings are correct.
• Press "Done" button.

ICQ (versions older than 99a only !) doesn't work correctly behind proxy server if it is unable to get the IP address of the ICQ communication servers (icq.mirabilis.com). You can solve the problem if you fill in the list of servers the ICQ is using also their IP addresses. First you have to detect the IP address of some server. You can do so easily using the ping.exe command from the DOS prompt window in Windows.
Run on the PC with active connection to Internet from Start menu program "Command prompt" and in the DOS window command ping icq.mirabilis.com. In the first line of the reply the program writes in crotchets the IP address of the server. The other lines are not interesting. Because the name icq.mirabilis.com is serving to more PCs repeating the ping command you get several different IP addresses.

4.5 Mapped Links

4.5.1 Setting the News

Type: - select the TCP type.

Proxy Port: - you have to choose a port number here. The only condition is that the number must be from the range 1-65535 and it must not be used on a PC running Proxy+ by any other program. If you use only one mapped link for News (or you define a first connection for News) you may with advantage use the number 119.

Target host: news.server.com:119

Press the Add button. In the list of mapped links Defined Links a new entry appears. Changes made in the settings are applied after restart of Proxy+.

Target host: irc.server.com:6667

4.6 Access List

Proxy+ v 2.30 (build #99) and higher has a possibility to restrict any services. It's based on Access Lists.  Evaluation of these Access Lists makes it possible to build complex rules.

Basic features of Access Lists:

• two levels of Access Lists definition  - first Access List Objects (ALO) are defined. Then Access List Rules (ALR) are build from them.
• variability - Access List Objects can be arbitrary combined in Access List Rules.
• The system is designed to be easily extendable with new ALOs in the future..

4.6.1 Access List Objects (ALO)

Access List Objects are elementary pieces of Access List Rules. Every ALO defines condition which is tested during ALR evaluation. Result of this ALO influences validity of whole ALR. Condition for the ALO is defined by its parameter which specifies allowed range of tested values (e.g. list of client computers IPs, list of destination URLs etc.).

Every ALO is defined by these elements:

• object name - text string (max 20 characters). You can use these characters only: 0'..'9', 'a'..'z', 'A'..'Z',   '.' '-' a '_' . Name is NOT case sensitive and it MUST be unique.
• object type - one of predefined types: ClientIP, InterfaceIP, URL, AdminURL, ContentType, Time, ServiceName, Parameter, UserLogin, HTTPRequest, RewriteWith.
• object parameter - defines ALO "value" which is used for evaluation of ALO validity. Every ALO MUST have one valid parameter at least.

General rules for ALO parameters specification:

• Each object can have more than one parameter defined. All parameters are separated by coma (if the parameters are in a file on a disc, each parameter must be on a separate line).
• The char ',' (coma) mustn't be a part of the parameter. In regular expressions there is a workaround for it. You can escape the coma using \xnn definition (see Regular expressions). The coma has value 44 (decimal representation) in the ASCII table. The hexadecimal value is x2C so we can use \x2C instead of  ',' character in regular expressions. It secures the Proxy+ will not recognize the character as parameter separator.
  In normal text parameters there is no way to escape the coma character. Each coma is   treated as parameter separator everytime.
• Each parameter can start with "!", that will cause the negation of the former parameter.

Parameters can be stored in the textual file. In the case following conditions have to be met:

• the file is textual and it must use Windows native textual file format. It means every line must end with CRLF sequence (you can use Notepad to edit the file for example).
• each parameter has to be on separate line. It means there must be no ',' (coma) in the line.
• line starting with '##' characters is ignored - you can use the sign to write comments.
• empty lines are ignored.
• when the file contains a line with ',' (coma) or the line is longer than 1024 characters then Proxy+ aborts loading the file.
• Proxy+ loads only first 1000 parameters from the file.

General rules of ALO evaluation:
ALO is evaluated as valid during ALR evaluation if at least one of its parameters meet the current request.

Predefined ALO types:
Proxy+ predefines these ALO types: ClientIP, InterfaceIP, URL, AdminURL, ContentType, Time, ServiceName, Parameter, UserLogin, HTTPRequest, RewriteWith. Following text describes them in detail:

• ClientIP

  Description:
  ALO of this type specifies clients (computers which generate requests) based on their IP address. For example it can be used to restrict access to Proxy+ functions to specified computers on local network only.

  Parameter:
  IP address can be specified in several ways. The range of validity can be inverted by "!" character. For example: 192.168.0.1 means that condition is valid if the request comes from computer with IP 192.168.0.1, whereas !192.168.0.1 means that condition is valid if the request doesn't come from computer with IP 192.168.0.1.

  a) single IP address
  IP address of single computer is specified as parameter.

  Example:
  192.168.0.10 - computer with specified IP address
  192.168.0.10, 192.168.0.25 - computers with specified IP addresses
  !192.168.0.10 - all computers except the one with specified IP address

  b) range of IP addresses
  range of addresses specifies lower and upper values of range separated by "-" character.

  Example:
  192.168.0-192.168.0.32
  192.168.100-192.168.0.150, 192.168.0.200-192.168.1.0
  !192.168.0.0-192.168.0.32

  c) range specified by network address and subnet mask
  it's standard way of IP addresses range definition. Network address and mask are separated by "/" character.

  Example:
  192.168.0.0/255.255.255.0
  192.168.0.0/255.255.255.240, 192.168.1.0/255.255.255.0
  !192.168.0.0/255.255.255.0

  d) range specified by network address and number of valid bits of address from the left
  its another commonly used format. Network address and number of valid bits are separated by "/" character. Number of valid bits is from range 0..32.

  Example:
  192.168.0.0/24
  192.168.0.0/30, 192.168.1.0/24
  !192.168.0.0/24
   

• InterfaceIP

  Description:
  ALO of this type allows/denies access according to an address of an interface through which the request comes to computer with the Proxy+ (analogy to Secure Interfaces). Its easy to deny access to the Proxy+ from the Internet by allowing access only through local network interface (Ethernet card).
  Meaning and usage is the same as in the ClientIP object type.

  Warning:
  If you want to allow/deny access even from the computer on which the Proxy+ is running it's necessary to specify IP address 127.0.0.1 (localhost) too.
   

• Time

  Description:
  Time specification influences validity or ALR according to time.

  Parameter:
  Parameter of this ALO specifies time range during which the ALO is valid. Format of this parameter is following:
  D:H:M where D stands for name of weekday or its abbreviation, H stands for hour from range 0..23 and M stands for minute from range 0..59. Any part (D, H on M) can be omitted and then its value is any from its range.

  Example:
  Monday:14:05 - every Monday at 2:05 PM.
  Mo:00:00 - every Midnight from Sunday to Monday
  16:20 - every day at 4:20 PM.
  Wed:: - every Wednesday, whole day
  Friday:15: - every Friday, from 3:00 PM to 3:59 PM.

  a) time range specified by the start time and the end time
  Parameter is specified by the start time and the end time of the range separated by "-" character.

  Example:
  Mon:7:30-Fri:16:00 - from Monday 7:30 am to Friday 4:00 PM
  13:00-17:00 - every day from 1:00 PM to 5:00 PM
  !Wed:: - whole week except Wednesday

  b) time range specified by the start time and the duration
  The requested range is defined by the start time and the duration separated by "/" character. The duration is in format H:M, where H is the hour in the range 0..23 and M is the minute in the range 0..59. The longest range is then 23 hours 59 minutes.

  Example:
  Monday:16:20/4:00 - start time on Monday at 4:20 p.m., duration 4 hours
  !10:00/35 - always true except for 35 minutes starting at 10:00 a.m. each day
   

• URL

  Description:
  Its purpose is to allow/deny access either to specified URL (e.g. WWW page address) or to specified server.
  Notice: This object type never applies to WWW Administrator interface - invalid setting doesn't temper the access to the administration of Proxy+.

  Parameter:
  Text string which is compared to name of document (for services which support requesting of concrete documents - www, HTTP Proxy, FTP Proxy, Gopher Proxy) or to name of destination computer (for services which support server specification only - Telnet Gateway, Mapped Links, ...).
  The parameter can contain wildcards "*" which stand for any other characters. Or the parameter can contain more powerful regular expression.

  Examples:
  http://www.server.com  - all URL addresses starting with http://www.server.com
  http://www.server.com/directory  - all URL addresses starting with http://www.server.com/directory
  http://www.server.com/document.html  - document with address: http://www.server.com/document.html
  *.gif, *.jpg  - all files with URL ending with *.gif or *.jpg
  */cgi-bin/*  - all files with URL containing text /cgi-bin/
  !*.gif  - all files with extension different from .gif
   

• AdminURL

  Description:
  Analogy to URL object type with the difference that AdminURL applies only to pages of administrator interface of Proxy+.
   

• ContentType

  Description:
  This object allows to restrict access to data files on WWW servers according to their types. WWW server sends a header first which should contain definition of file type (in Content-Type field). Proxy+ allows comparison of the type of the file and the type defined in the ALO definition and thus allow/deny retrieving of the object.

  Object type is defined as type/subtype by WWW server, where type specifies main type of object and subtype specifies kind of type. For example file containing ordinary WWW page has type text/html, text file (with TXT extension) as type text/plain.

  List of mostly used types of files on WWW servers:
  text/html, text/plain   - text files
  image/gif, image/jpg  - image files
  application/octet-stream, application/msword  - data files (e.g. executable .EXE files, etc)

  Parameter:
  Text specifying mask which is compared to type obtained from Content-Type line of file header. It can contain wildcards "*" which stand for any characters. Or the parameter can contain more powerful regular expression.

  Example:
  application/* - all files marked as applications by the WWW server.
  !image/* - all files non marked as images.
  text/html - files with WWW pages only.
   

• ServiceName

  Description:
  Allows/denies access to Proxy+ service by internal service name.

  List of Proxy+ services:

  ADMIN	WWW interface for administrator to change Proxy+ settings.
  FTP	FTP Proxy - accepts requests on the same port as HTTP proxy does (4480). WWW browsers use this service.
  FTPG	FTP Gateway - gateway for communication between FTP clients and FTP servers
  GOPHER	Gopher Proxy - accepts requests on the same port as HTTP proxy does (4480). WWW browsers use this service.
  HTTP	HTTP Proxy - accepts requests from WWW browsers for getting data from WWW servers over the Internet.
  HTTPS	Analogy to HTTP Proxy, it works with encrypted (secured) data transmission.
  ICP	ICP (Inter Cache Protocol) Server which increases effectivity of cooperating proxy servers.
  MAPPED	Mapped Links.
  SOCKS4	SOCKS4 protocol which enables access to the Internet to applications whose own communication protocol is not supported by proxy servers (IRC, Telnet, ...)
  SOCKS5	SOCKS5 enhances service of SOCKS4 protocol by UDP support.
  RAUDIO	Real Audio Proxy (PNA Proxy) - serves for transfer of audio and/or video.
  TELNET	Telnet Gateway.
  WWW	Internal WWW server of Proxy+.

  Parameter:
  Name of service (or comma separated names). Its possible to use wildcards "*" in the name of service. Or the parameter can contain more powerful regular expression.

  Example:
  HTTP  allow access over HTTP proxy interface
  HTTP* allow access over HTTP and HTTPS proxy interface
  !HTT*,FTP,Gopher  deny access to HTTP Proxy, HTTPS Proxy,FTP Proxy and Gopher Proxy services 
  

• Parameter

  Description:
  This ALO is special. It defines parameter to be passed to Proxy+ service in case that Pass action is result of ALR evaluation (hidden completing of request for username and password).
  ALR line describing Pass action is valid if Parameter ALO is specified on the line.

  Parameter:
  Text which will be passed to running Proxy+ service in case the line with ALR containing this object type is evaluated as valid (true).

  Setting username and password for automatic access authentication on WWW server:
  Syntax:
  username : password ( ! without blanks ! )

  Example:
  user:passwd1 - example of parameter for Pass action - the request will be completed as if the user sets name user and password passwd1.
  

• UserLogin
  
  Description:
  This access list object allows to restrict user access according to specified name and password.
  If the UserLogin object is used in Access List rules, Proxy+ automatically sends a request for name and password to the browser in case that the UserLogin object is evaluated as invalid. A browser should display a dialog where the users can specify the login credentials. If the line with a UserLogin object is not reached during the Access List Rules processing, the browser does not have to send credentials. It's possible to turn on sending of the request by changing the HTTP Proxy authentication setting on the Proxy Settings\Proxies\HTTP Proxy page of the WWW Admin interface.
  
  Parameter:
  A text defining a list of allowed names and passwords. Credential pair is a colon ":" separated value of name:password and these pairs are coma "," separated. A name and a password can be empty (alone colon) or checking against local accounts can be used.
  
  Syntax:
  name:password
  
  Following applies:
  - there must not be an extra space between the name and the colon and between the colon and the password.
  - the name and the password must not contain a colon character.
  
  Special values:
  :local: - perform check against the local accounts.
  :: - (two colons without spaces) same as previous.
  
  Example:
  john:secret - the object is evaluated as valid only if the user uses john as a name and secret as a password.
  john:secret,john:,:: - the object is evaluated as valid only if the user uses john as a name and secret as a password or uses john as a name and an empty password or the user is defined in the local accounts.
  !john:secret,:local: - the object is evaluated as valid only if the user uses a name other than john/secret or the user is defined in the local accounts (the example only demonstrates usage of '!' in the object. In the real world the example is not usable. But maybe..).
  
  
• HTTPRequest
  
  Description:
  This object allows (in conjunction with RewriteWith object) to rewrite a URL address (or a whole browser request line) which a browser requests from Proxy+ and redirect this to some other address (other WWW server).
  This object type defines the part of a URL which will be replaced. The RewriteWith object defines the replacement.

  The HTTPRequest object can be used instead of URL object too. Because it gets all the first line of browser request as the input (including HTTP method definition) it can depend on method name or HTTP protocol version (you can create an accesslist which allows only GET requests for example).

  Whole first line of the browser request is on the input. This line contains three parts: an HTTP method definition (GET, POST, PUT, HEAD, ...), an document address definition (including parameters) and a version of used protocol. This line usually looks like this:

  GET http://www.server.com/directory/document.htm HTTP/1.1
  
  (note: the document part contains servername and protocol definition everytime. It is because the browser is sending the request through proxy. URLs which doesn't contain protocol or server definition aren't valid and Proxy+ generates an error message in the case).

  The HTTPRequest object can specify any part of the line to be rewritten, mostly first two. If the object parameter value is not found (or the request head doesn't match a regular expression definition) the object is evaluated as invalid and a rewriting rule is not applied.

  Note: if you are using HTTPRequest object to rewrite the request it's good to mix it with an URL object  (or another HTTPRequest which is declared in the rule line before the object defining the part of request which should be rewritten) - and thus limit the URLs which could be rewritten.

  Parameter:
  A text defining what will be replaced by a RewriteWith object parameter value or the text which has to be found in the input.
  You can use plain text (usable in limited number of cases) or likely more complex and powerful regular expressions.

  The object became valid if the keyword in its parameter field is found in the input or the input matched a regular expression.

  For plain text following applies:
  - it's not possible to use wildcards (the '*' doesn't mean a wild-card, it is a regular character). E.g. 'www.server.com/*' will try to find a text containing an asterisk.
  - search is NOT case sensitive (if you are using regular expression you can use (?-i) modifier to interpret the expression case sensitively).

  Common conditions apply to regular expressions (see regular expressions). We advise to use built-in RegExp helper to test regular expressions.

  Syntax:
  plain text or regular expression
  
  Examples:

  Description	HTTPRequest	RewriteWith
  Denying of the EXE files (replace all HTTP requests for getting EXE file by link to an HTML page on different WWW server)	~.*\shttp://.*/.*\.exe(\s.*)	GET http://192.168.0.1/accessdenied.htm$1
  Redirect accesses to www.server.com to other address (www.myserver.com)	~(.*\s.*://)www\.server\.com(/.*\s.*)	$1www.myserver.com$2
  Denying of using IP addresses of WWW servers in requests (replace all links using IP addresses by an error message)	~.*\s.*://(\d{1,3}\.){3}\d{1,3}.*(\s.*)	GET http://myserver.com/accessdenied.htm$2

  Note: all reqular expressions must be started with '~' or '/r' or '/R'. In other case the expression are evaluated as as usuall wildcard string.

• RewriteWith
  
  Description:
  This access object defines the text which will be used as a replacement of a text defined in a HTTPRequest Object used within Rewr ACL rule.
  It's nonsense to use a RewriteWith object alone or within other than Rewr rule (the object is always evaluated as valid).
  Note: if more than one HTTPRequest object is used on the same line with RewriteWith object, all HTTPRequest objects must be evaluated as valid and only the last one will be used as a template for rewriting.
  
  Parameter:
  Definition of a text which will be used as a replacement of the text specified by an HTTPRequest object. It's possible to use back references to subexpressions by $n, where n is 1,2,3,4, ... (note: 0 means whole regular expression).
  
  Examples:
  See examples above in the HTTPRequest object