# Demo configuration for InteProxy. # # This file defines how different remote servers are to be accessed. # All servers are specified by URLs in the inteproxy-rules section. # # For backwards compatibility, an older format is also supported where # each server is defined by one section for each remote server. How the # sections are named doesn't really matter but it's a good idea to # include the full domain name in the section name. If you want to # access to different servers on the same host, be careful to give both # sections different names, by e.g. appending some more information # about the server. # # There might be some additional section with predefined names in the # future for other inteproxy settings. The names for those section will # be chosen so as to not interfere with existing section names. Hence # the suggestion to use the full domain name. # # InteProxy-related configuration-entries follow # !! IMPORTANT: # !! If you need upstream proxy-authentification, please uncomment the # !! following entries [inteproxy] and [http_proxy_authentification] and # !! adopt them with your credentials! # Authentification against upstream proxy-servers [inteproxy] # https_proxy=http_proxy_authentification # http_proxy=http_proxy_authentification # Uncomment the following line to suppress an upcoming popup that shows fees and # access constraints. Allowed values for show_terms_dialog option are "false", # "no" and "0" to suppress the popup, "true", "yes" and "1" to show the popup. # The default is "true". # # show_terms_dialog=false # Uncomment the following line to validate the servers SSL certificate. # Allowed values for do_certificate_validation # option are "false", "no" and "0" to disable validation, "true", # "yes" and "1" to enable validation. The default is "false". # This feature will only work when using Python Version 2.6 or later. # # do_certificate_validation=True # # The path to a file that contains certification authority certificates which # are used to validate certificates passed from the remote server. # cacerts=/path/to/cacerts.crt # [http_proxy_authentification] # host=upstream.proxy.url.com # port=8080 # username=john # password=secret # Main rules section. The urls setting is a list of urls, one on each # line. From the second line on, the lines have to be indented. # Each url is of the form # SCHEME://[USER:PASSWORD@]HOSTNAME[:PORT]/PATH # # The credentials (USER and PASSWORD) and the port number (PORT) are # optional. If no port is given a default is assumed. # SCHEME should be one of the supported schemes: # # owsproxy The remote host is an OWSProxy requiring authentication # and https # # basicauth HTTP Basic Authorization over https # # If USERNAME or PASSWORD contain special characters such as '%', ':', # '@' and non-ascii characters, these should be escaped as "%" followed # by the two hexadecimal digits of the character code. As a further # complication, the percent character is not only special in URLs, but # also in the syntax used in this configuration file where a literal # percent character has to be quoted by doubling it. So to encode # e.g. percent sign, use "%%25" instead of simply "%". # # The HOSTNAME and PATH parts of the URL may contain "*" characters as # wild-cards. They will match zero or more occurrances of any # character. However, a wild-card in the hostname will only match in # the hostname and a wild-card in the path will only match in the path. [inteproxy-rules] urls=owsproxy://meier:meier@inteproxy-demo.intevation.org/cgi-bin/frida-wms owsproxy://USERNAME:PASSWORT@www.geobasisdaten.niedersachsen.de/mapgate/*