|
This document deal with the frequently asked questions ;-) |
| Dates de modification | ||
|---|---|---|
|
|
|
|
|
|
|
|
This is often because the authentication layer is not well configured or you are not allowed to access the resource. Configure carefully your build.properties file.
Watch the server logs - a successfull request is like :
TP-Processor51, 03-mars-2006 11:11:48, bourges, PROPFIND, 207 "Multi-Status", 7 ms, /files/injac/res_proj_cri/
bourges is the connected user - if it is written unauthenticated, either you access the server using the unauthenticated mode or you authentication layer is not well configured. Note that while accessing an inJAC space the ESUP channel storage use a special user with root privileges.
PROPFIND is the WebDAV request
207 HTTP response - it could be for example a 507 (quota exceeded) or 403 (forbidden) response
/files/injac/res_proj_cri/ is the resource URI
If you have problems with just some webdav clients, look at Recommended configuration section of Installation chapter
In order to resolve the encodage problems, you must specify the encodage needed at the server.
setenv LANG "fr_FR.utf8" setenv LANGUAGE "fr_FR.utf8"
A long time ago, in a galaxy far far away, the administration client was designed to be run using a graphical user interface or a command-line mode.
The G.U.I. had to be run using the run.* -gr command and the command-line mode using the run.* -cl command.
But only the command-line mode is currently implemented.
It is often due to a wrong pattern file. You will find a good sample file in the user guide.
Nothing is wrong. The ESUP WebDAV server has a soft quota management system. It means that a quota can be exceeded at most 1 time.
The killing question is : "Why having developped such a quota management system ?"
We did not intend to develop a soft quota management system. The problem is that the quota listener relies on the content-length HTTP header to check if a resource to put/copied/moved on the server will leads to an overquota. But the content-length HTTP header is optionnal and in this way, the listener can not check the overquota "on the fly" and just check if the quota was already exceeded just before the action in progress.
One can use another Tomcat server than that provided in package. Nevertheless, one must modify the server.xml file of Tomcat. (The additions are in bold)
<Connector port="8080" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" debug="0" connectionTimeout="20000" disableUploadTimeout="true" URIEncoding="UTF-8"/> <Connector port="8009" enableLookups="false" redirectPort="8443" debug="0" protocol="AJP/1.3" URIEncoding="UTF-8"/>