Changes

From SME Server
Jump to navigationJump to search

SME Server:Documentation:FAQ/fr (view source)

Revision as of 23:40, 20 March 2017

1,109 bytes added ,  23:40, 20 March 2017
→‎Spamassassin
Line 918: Line 918:     
Sur un serveur SME, cela devrait fonctionner avec '''<tt><nowiki>export http_proxy='http://localhost:3128'</nowiki></tt>''', qui nécessiterait d'être ajouté à /etc/cron.daily/sa_update
 
Sur un serveur SME, cela devrait fonctionner avec '''<tt><nowiki>export http_proxy='http://localhost:3128'</nowiki></tt>''', qui nécessiterait d'être ajouté à /etc/cron.daily/sa_update
 +
 +
===curl, wget===
 +
For curl and wget to work correctly on a SME server without direct internet access, you must execute the following command in the same program or shell session beforehand:
 +
 +
export http_proxy=localhost:3128
 +
 +
eg:
 +
<nowiki>export http_proxy=localhost:3128
 +
curl http://www.google.com</nowiki>
 +
 +
===ssh, ftp, telnet===
 +
{{Note box|ssh, ftp and telnet do not work via an http "upstream" proxy, although they may work in conjunction with [http://linux.die.net/man/8/tsocks tsocks] (available from the dag repository)}}
 +
 +
===Testing and Verification===
 +
You can verify that a particular program is being proxied through squid on your local SME server by searching /var/log/squid/access.log for access to the target web address originating from '127.0.0.1'.
 +
 +
That is, after executing these commands:
 +
<nowiki>export http_proxy=localhost:3128
 +
curl http://www.google.com</nowiki>
 +
 +
you should see an entry similary to the following <tt>/var/log/squid/access.log:</tt>
 +
1329759611.923    64 '''127.0.0.1''' TCP_MISS/301 726 GET '''<nowiki>http://www.google.com</nowiki>''' - DIRECT/74.125.113.94 text/html
    
==Memory usage and limits==
 
==Memory usage and limits==
Gieres
3,113

edits

Retrieved from "https://wiki.koozali.org/Special:MobileDiff/32978"

Navigation menu