Ignore:
Timestamp:
11/11/11 13:17:43 (19 months ago)
Author:
BrainSlayer
Message:

update proftp

File:
1 edited

Legend:

Unmodified
Added
Removed
  • src/router/proftpd/doc/modules/mod_lang.html

    r14672 r17876  
    1 <!-- $Id: mod_lang.html,v 1.7 2009/12/11 01:06:18 castaglia Exp $ --> 
     1<!-- $Id: mod_lang.html,v 1.8 2010/08/10 17:39:08 castaglia Exp $ --> 
    22<!-- $Source: /cvsroot/proftp/proftpd/doc/modules/mod_lang.html,v $ --> 
    33 
     
    219219</ul> 
    220220 
     221<p><a name="FAQ"></a> 
     222<b>Frequently Asked Questions</b><br> 
     223 
     224<p><a name="SpecialCharacters"> 
     225<font color=red>Question</font>: When I upload a file with special characters 
     226(<i>e.g.</i> umlauts, accents, cedillas, <i>etc</i>), the special characters 
     227are turned into '?' on the server.  What's wrong?<br> 
     228<font color=blue>Answer</font>: There are a couple of things to check when 
     229this happens. 
     230 
     231<p> 
     232First, make sure that your <code>proftpd</code> has been compiled with NLS 
     233support.  Type <code>proftpd -V</code>, and make sure you see: 
     234<pre> 
     235  + NLS support 
     236</pre> 
     237appear in the output. 
     238 
     239<p> 
     240Next, make sure that the <code>LANG</code> environment variable is set before 
     241starting the server.  Special characters require that UTF8 or ISO-8859-1 be 
     242used, thus you might use things like: 
     243<pre> 
     244  # export LANG=de_DE.utf8 
     245  # export LANG=fr_FR.ISO8859-1 
     246</pre> 
     247 
     248<p> 
     249Last, check that any routers/firewalls/NAT between the clients and the server 
     250are not interfering.  ProFTPD lists "UTF8" in its <code>FEAT</code> response 
     251data; many FTP clients use the <code>OPTS UTF8 ON</code> command to inform the 
     252server that UTF8 filenames will be sent.  Some routers, firewalls, and NATs 
     253have been known to filter both the <code>FEAT</code> response and/or block 
     254commands like <code>OPTS UTF8</code>, thus interfering with the protocol and 
     255causing encoding problems. 
     256 
    221257<p> 
    222258<hr><br> 
    223259Author: <i>$Author: castaglia $</i><br> 
    224 Last Updated: <i>$Date: 2009/12/11 01:06:18 $</i><br> 
     260Last Updated: <i>$Date: 2010/08/10 17:39:08 $</i><br> 
    225261<br><hr> 
    226262 
    227263<font size=2><b><i> 
    228 &copy; Copyright 2006-2008 TJ Saunders<br> 
     264&copy; Copyright 2006-2010 TJ Saunders<br> 
    229265 All Rights Reserved<br> 
    230266</i></b></font> 
Note: See TracChangeset for help on using the changeset viewer.