Proxy Settings
: With this you can specify if YaCy can be used as transparent proxy.
Hint: On linux you can configure your firewall to transparently redirect all http traffic through yacy using this iptables rule:
iptables -t nat -A PREROUTING -p tcp -s 192.168.0.0/16 --dport 80 -j DNAT --to 192.168.0.1:#[port]#
: If unchecked, the proxy will act using Cache Fresh / Cache Stale rules. If checked, the cache is always fresh which means that a page is never loaded again if it was already stored in the cache. However, if the page does not exist in the cache, it will be loaded in any case.
: Specifies if the proxy should send the Via http header according to RFC 2616 Sect 14.45.
: Specifies if the proxy should send the X-Forwarded-For http header.
Proxy Access Settings

These settings configure the access method to your own http proxy and server. All traffic is routed throug one single port, for both proxy and server.

#(server.https)#:: #(/server.https)#
HTTP Server Port: #[port]#  HTTPS Server Port:  

Server Access Restrictions

You can restrict the access to this proxy/server using a two-stage security barrier:

This is the account that restricts access to the proxy function. You probably don't want to share the proxy to the internet, so you should set the IP-Number Access Domain to a pattern that corresponds to you local intranet. The default setting should be right in most cases. If you want, you can also set a proxy account so that every proxy user must authenticate first, but this is rather unusual.

:
: Use Proxy Accounts