RE: custom authentication with slide and httpclient
Hello Aaron, Lately I have been very upset by that 'expect: continue' handshake. I'll just link you with my results in this urls: http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.dotnet .frameworkmid=a515168f-df63-4ff3-8e2b-ec7f6fb76c0a http://issues.apache.org/bugzilla/show_bug.cgi?id=31567 In short, there seems to be an exploit Micro$oft found about to make their http 1.1 implementation incompatible with tomcat 5.0.28 (at least this version it's true). Seems like M$ uses the 'expect: continue' header for authentication handshake but instead of waiting for the response, from the remote server, before starting to send the body content, it starts to send the body content anyway. That is bad because tomcat replies with an obvious 401 Unauthorized, and for the following HTTP request it uses the data from the body content from the previous request as the start of the following request. That results in another error response 505 HTTP Version Not Supported. In those links I complained to M$ and they just told me to disable the 'expect' headers (LOL), and to Tomcat, Remy just wasn't very reasonable to make an enhancement (discard the data of the invalid content body) witch I though it was the right thing to do... It was just a warning about the expect headers. Best regards, Miguel Figueiredo Hi Aaron, See my comments in-line On Mon, 2005-02-07 at 10:49 -0500, Aaron Hamid wrote: Hi folks, sorry for the cross posting but I think this issue is relevant to both projects. snip There are two problems I have found, one in http client, one in Slide. First, it seems that CredentialsProvider ONLY is called upon a challenge from the server (HttpMethodDirector, 'promptForCredentials'), and never pre-emptively, even if I setAuthenticationPreemptive(true). My expectation would be that if I set preemptive authentication than my registered CredentialsProvider should be called prior to the request being made. Our custom auth doesn't use an HTTP challenge, so the creds are required to be there to begin with. I can explain this. The problem is that only Basic authentication can be used preemptively and required by HTTP spec for compatibility reasons. All other schemes either cannot be used preemptively (NTLM) or should not be used preemptively (Digest to some extent). Firstly, challenge-less authentication schemes are inherently insecure, because they allow the authentication credentials to be sent to an unknown party. Even if the credentials are encrypted using a predefined encryption algorithm, one can still easily pull off a 'man in the middle' type of exploit. Secondly, the so called 'expect: continue' handshake renders the preemptive authentication virtually superfluous. For a fairly small price one gains a lot in terms of security. Bottom line, if your web server supports HTTP/1.1, which is a commonplace these days, disable the preemptive authentication, enable the 'expect: continue' handshake and live happily ever after. In addition, it seems that the HTTP Method implementations of Slide use a default AuthState (in HttpMethodBase). Apparently it uses BASIC auth as the default scheme, and does not pick up the global defaults (I tried registering my parameters on the DefaultParams* singleton after discovering this, to see if they would be picked up, but they are not). I do not know much about Slide's inner working, but I'll be willing to take a look at the Slide source code, should this be required. I think the first quick fix is to update HttpMethodDirector so it uses CredentialsProvider preemptively (if one is defined, and setAuthenticationPreemptive is set). See above. I'm not sure how to handle the second problem because I am not thoroughly familiar with the design decisions and abstractions behind HttpClient and expected usage. I would think either the Slide WebdavResource should expose the HttpClient with the real AuthState it will use (I know I can get HttpClient through WebdavSession.getSessionInstance... but it appears the default AuthState in the Method overrides anything I set), or have the default authstate inherit global defaults (perhaps lazily). See above. Cheers, Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
versioncontrol-exclude for subfolders
Hi List i want to exclude a folder and all subfolders from versioncontrol. the folder should be a temporary file dump. but if I set parameter name=versioncontrol-exclude/files/temp/parameter and i create a new folder in /files/temp/ lets say /files/temp/first first will be version controlled. is there a possibility to say this folder an all subfolders shouldbe excluded from version control? using * as wildcard doesn't seem to work thanks in advance SVen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: versioncontrol-exclude for subfolders
it seems like there is another problem. it looks like versioncontrol-exclude is not only for the specified folder, but also for the subfolders. my problem seems to be that i want to set more then one folder to be excluded from version control. it looks like that: /slide/files/users should be excluded /slide/files/public should be excluded /slide/files/system should be under version control is this possible, or do i have to set auto-version-control to false? thanks in advance SVen -Original Message- From: Sven Pfeiffer [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 09, 2005 11:37 AM To: Slide Users Mailing List (E-mail) Subject: versioncontrol-exclude for subfolders Hi List i want to exclude a folder and all subfolders from versioncontrol. the folder should be a temporary file dump. but if I set parameter name=versioncontrol-exclude/files/temp/parameter and i create a new folder in /files/temp/ lets say /files/temp/first first will be version controlled. is there a possibility to say this folder an all subfolders shouldbe excluded from version control? using * as wildcard doesn't seem to work thanks in advance SVen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: A question on Http Connection obtained by WebdavResoruce
Warwick, Thanks for your reply. The HttpConnection that I am referring to is method.releaseConnection() after the method is executed. Calling this method would just close the current request and not re-set the HttpClient state. In other words the HttpClient will still hold on to any cookies from the previous handshake and the next Method execution would not have to re-authenticate. So you would still be able to use the same WebdavResource by setting a new path to perform another operation. Calling releaseConnection may also be useful for uploading files with Transfer-Encoding:Chunked. Certain WebServers/AppServers expect an explicit client close connection as an indication for end of stream. Could there be any other reason for not releasing the connection? Or is this just an oversight? Thanks, Ritu -Original Message- From: Warwick Burrows [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 08, 2005 9:54 PM To: Slide Users Mailing List Subject: RE: A question on Http Connection obtained by WebdavResoruce I believe this was a design choice to allow connections to be reused (persistent connections) rather than opening/closing a connection on every DAV method call. For example I have one webdavresource per thread and reuse the webdavresource by making use of the setPath() command to change the resource target for the webdavresource or by using the methods that take a path to specify which resource is the target of the method call. Warwick -Original Message- From: Ritu Kedia [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 08, 2005 1:36 AM To: Slide Users Mailing List (E-mail) Subject: A question on Http Connection obtained by WebdavResoruce Hello, I was looking into a caching solution to cache the WebdavResource obtained for a user so as to avoid the time taken to re-authenticate that user to Slide App. In doing so I came across the way the HttpClient is managed by the WebdavResource. After execution of any method the HttpConnection is not being released. Is there any specific reason for this? On Commons HttpClient site(http://jakarta.apache.org/commons/httpclient/tutorial.htm l) it is mentioned that It is important to always release the connection regardless of whether the server returned an error or not. If the connection is not released when will it be closed by default? I believe that would depend on the ConnectionTimeout setting of HttpClient. However I saw that in WebdavSession the timeout is not being explicitly set, so the default value of 0 must be applied. In this case when would the connection be closed? Would it then depend on the server timeout settings? Anyone having any knowledge of these issues, please do reply. Thanks, Ritu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: versioncontrol-exclude for subfolders
Hi Sven, please try parameter name=versioncontrol-exclude/slide/files/users;/slide/files/public/pa rameter Regards, Peter -Original Message- From: Sven Pfeiffer [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. Februar 2005 11:48 To: Slide Users Mailing List Subject: RE: versioncontrol-exclude for subfolders it seems like there is another problem. it looks like versioncontrol-exclude is not only for the specified folder, but also for the subfolders. my problem seems to be that i want to set more then one folder to be excluded from version control. it looks like that: /slide/files/users should be excluded /slide/files/public should be excluded /slide/files/system should be under version control is this possible, or do i have to set auto-version-control to false? thanks in advance SVen -Original Message- From: Sven Pfeiffer [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 09, 2005 11:37 AM To: Slide Users Mailing List (E-mail) Subject: versioncontrol-exclude for subfolders Hi List i want to exclude a folder and all subfolders from versioncontrol. the folder should be a temporary file dump. but if I set parameter name=versioncontrol-exclude/files/temp/parameter and i create a new folder in /files/temp/ lets say /files/temp/first first will be version controlled. is there a possibility to say this folder an all subfolders shouldbe excluded from version control? using * as wildcard doesn't seem to work thanks in advance SVen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: failed to programatically upload file
Hello Clive,
I followed your suggestion and it worked! Thanks a lot.
So the wdr.putMethod(fileName) will work only if passed the complete URL to
the Slide server concatenated with the name of the file to upload? If yes,
this is not very clearly documented...
Regards,
Zoltan
Hi,
I had the same problem; try doing the following:
File fn = new File(fileName);
String path = http://localhost:8080/slide/files/; + fn.getName();
wdr.putMethod(path, fn);
Hope that helps!
Clive
Hello,
I have downloaded and deployed slide.war to my Jboss 4.0.1 deploy folder
(under Windows XP SP1).
On the client side, I have jakarta-slide-webdavlib-2.1.jar in my build path.
I've tried to upload a file using the following snippet of code:
try
{
HttpURL hrl = new HttpURL(url);
WebdavResource wdr = new WebdavResource(hrl);
File fn = new File(fileName);
wdr.putMethod(fn);
wdr.close();
}
catch(MalformedURLException mue)
{
String msg = (UploadFile) execute : wrong fileName passed: +
fileName;
log.debug (msg, mue);
}
catch(HttpException he)
{
String msg = (UploadFile) execute : HTTP exception occured ;
log.debug (msg, he);
}
catch(IOException ioe)
{
String msg = (UploadFile) execute : IO exception occured ;
log.debug (msg, ioe);
}
At run-time the url passed is : http://localhost:8080/slide/files and the
fileName is /DJ/images/16.jpg (the correct location of the file on my local
machine).
The upload fails and I see the following on the Jboss console:
12:05:31,359 INFO [STDOUT] http-0.0.0.0-8080-Processor24, 08-Feb-2005
12:05:31, unauthenticated, PROPFIND, 207 Multi-Status, 31 ms, /files
12:05:31,578 INFO [STDOUT] http-0.0.0.0-8080-Processor24, 08-Feb-2005
12:05:31, unauthenticated, PUT, 403 Forbidden, 0 ms, /files
I read some articles about authentication problems with Slide and, as a
result, I have modified the domain.xml file like:
permission action=all subject=/roles/root
inheritable=true/
permission action=/actions/read-acl subject=all
inheritable=true negative=true/
permission action=/actions/write-acl subject=all
inheritable=true negative=true/
permission action=/actions/unlock subject=all
inheritable=true negative=true/
permission action=/actions/read subject=all
inheritable=true/
!-- /users --
objectnode
classname=org.apache.slide.structure.SubjectNode uri=/users
permission action=all subject=self
inheritable=true/
!--permission action=all subject=unauthenticated
inheritable=true negative=true/--
permission action=/actions subject=/users/guest/
!-- /users/root represents the administrator --
objectnode
classname=org.apache.slide.structure.SubjectNode uri=/users/root
revision
property
namespace=http://jakarta.apache.org/slide/; name=password/
/revision
/objectnode
!-- /users/john and /users/john2 represent
authenticated users --
objectnode
classname=org.apache.slide.structure.SubjectNode uri=/users/john
revision
property
namespace=http://jakarta.apache.org/slide/; name=password/
/revision
/objectnode
objectnode
classname=org.apache.slide.structure.SubjectNode uri=/users/john2
revision
property
namespace=http://jakarta.apache.org/slide/; name=password/
/revision
/objectnode
!-- /users/guest represents an authenticated or
unauthenticated guest user --
objectnode
classname=org.apache.slide.structure.SubjectNode uri=/users/guest
revision
property
namespace=http://jakarta.apache.org/slide/; name=password/
/revision
/objectnode
/objectnode
Note: I don't have any problems in uploading the same file using the slide
client:
[LOCALHOST:/slide/files/] C:\jakarta-slide-webdavclient-bin-2.1\bin $ put
/dj/images/16.jpg
Could anyone tell me what do I do wrong? Is there a configuration issue?
Kind regards,
Zoltan Lazar
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Re: Duplicating security information?
Thanks for the response! If I go ahead with this, my plan is to mimick a good idea that Ben Alex had for his Acegi Security framework, which is to create an adapter that would implement the store interfaces (like JNDIPrincipalStore does), but translate and delegate to a simplified DAO that one could implement for various security backends. It is easy to adapt Acegi to your own security system because all you have to do is implement a simple DAO interface from Acegi - the same should be possible for Slide. As I look over the JNDIPrincipalStore implementation I can see there is a lot of Slide specific API protocol going on that I'm going to have to parse. A simple DAO interface would make this much easier. I'm not sure what the DAO interface is going to look like yet (it will be read only at this point, like the JNDIPrincipalStore), but it sure would be nice to have something as simple as this: Collection getUsers(... some sort of Slide related criteria ...) Collection getUserRoles(String username) It seems like such a common thing people want to do, it is will worth the effort of creating this interface. Well, I'm off to parse the Slide API... any tips are appreciated. :) - Andy On Tuesday 08 February 2005 07:00 pm, Carlos Villegas wrote: Andy Depue wrote: None of these options seem very palatable to me. Am I missing something? Does Slide really not provide an easy way for me to supply it with the currently authenticated user AND his/her roles? To me, the ideal solution would be to hand Slide a preauthenticated token of some sort that says, I've already authenticated this guy and vouch for him - oh, and btw, these are the roles he is granted. Any information or help in this area is greatly appreciated! No, there doesn't seem to be an easy way. You'll need to write your own store. You can take a look at the JNDIPrincipalStore which is close to what you want to do; it retrieves users and roles from an LDAP directory. There was an idea of writing a store that retrieves users and roles from a JAAS LoginModule which is a standard way to plugin different authentication systems. However, there are issues about how to map the WebDAV model to JAAS. JAAS handles authentication but it doesn't seem to provide a way to list all users and roles, which is needed by Slide. Anyway, I may take a look at this later, but I don't know when I'll be able to do that. Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: failed to programatically upload file
Hi Zoltan,
That is correct! I have found that Slide is not clearly documented; but
under the roadmap link on the website; slide documentation, snippets,
tutorials etc. is in progress. Hope that will shed some light on slide!
The problem I have encountered is large file transfer! (files 2GB) I have
applied the patch from Onion networks but I am still having issues.
So if anyone has done large file ( 2GB) uploads downloads using Jetty
Slide; please throw any suggestions my way!
Thanks,
Clive
-Original Message-
From: Zoltan [mailto:[EMAIL PROTECTED]
Sent: 09 February 2005 06:23 PM
To: 'Slide Users Mailing List'
Subject: RE: failed to programatically upload file
Hello Clive,
I followed your suggestion and it worked! Thanks a lot.
So the wdr.putMethod(fileName) will work only if passed the complete URL to
the Slide server concatenated with the name of the file to upload? If yes,
this is not very clearly documented...
Regards,
Zoltan
Hi,
I had the same problem; try doing the following:
File fn = new File(fileName);
String path = http://localhost:8080/slide/files/; + fn.getName();
wdr.putMethod(path, fn);
Hope that helps!
Clive
Hello,
I have downloaded and deployed slide.war to my Jboss 4.0.1 deploy folder
(under Windows XP SP1).
On the client side, I have jakarta-slide-webdavlib-2.1.jar in my build path.
I've tried to upload a file using the following snippet of code:
try
{
HttpURL hrl = new HttpURL(url);
WebdavResource wdr = new WebdavResource(hrl);
File fn = new File(fileName);
wdr.putMethod(fn);
wdr.close();
}
catch(MalformedURLException mue)
{
String msg = (UploadFile) execute : wrong fileName passed: +
fileName;
log.debug (msg, mue);
}
catch(HttpException he)
{
String msg = (UploadFile) execute : HTTP exception occured ;
log.debug (msg, he);
}
catch(IOException ioe)
{
String msg = (UploadFile) execute : IO exception occured ;
log.debug (msg, ioe);
}
At run-time the url passed is : http://localhost:8080/slide/files and the
fileName is /DJ/images/16.jpg (the correct location of the file on my local
machine).
The upload fails and I see the following on the Jboss console:
12:05:31,359 INFO [STDOUT] http-0.0.0.0-8080-Processor24, 08-Feb-2005
12:05:31, unauthenticated, PROPFIND, 207 Multi-Status, 31 ms, /files
12:05:31,578 INFO [STDOUT] http-0.0.0.0-8080-Processor24, 08-Feb-2005
12:05:31, unauthenticated, PUT, 403 Forbidden, 0 ms, /files
I read some articles about authentication problems with Slide and, as a
result, I have modified the domain.xml file like:
permission action=all subject=/roles/root
inheritable=true/
permission action=/actions/read-acl subject=all
inheritable=true negative=true/
permission action=/actions/write-acl subject=all
inheritable=true negative=true/
permission action=/actions/unlock subject=all
inheritable=true negative=true/
permission action=/actions/read subject=all
inheritable=true/
!-- /users --
objectnode
classname=org.apache.slide.structure.SubjectNode uri=/users
permission action=all subject=self
inheritable=true/
!--permission action=all subject=unauthenticated
inheritable=true negative=true/--
permission action=/actions subject=/users/guest/
!-- /users/root represents the administrator --
objectnode
classname=org.apache.slide.structure.SubjectNode uri=/users/root
revision
property
namespace=http://jakarta.apache.org/slide/; name=password/
/revision
/objectnode
!-- /users/john and /users/john2 represent
authenticated users --
objectnode
classname=org.apache.slide.structure.SubjectNode uri=/users/john
revision
property
namespace=http://jakarta.apache.org/slide/; name=password/
/revision
/objectnode
objectnode
classname=org.apache.slide.structure.SubjectNode uri=/users/john2
revision
property
namespace=http://jakarta.apache.org/slide/; name=password/
/revision
/objectnode
!-- /users/guest represents an authenticated or
unauthenticated guest user --
objectnode
classname=org.apache.slide.structure.SubjectNode uri=/users/guest
revision
property
namespace=http://jakarta.apache.org/slide/; name=password/
Line breaks in properties
Hi there! Here's the case. When I save a property like this: descriptor.setProperty( new NodeProperty(propertyName, propertyValue, propertyNamespace)); where a descriptor is an instance of the NodeRevisionDescriptor class and a propertyValue is a String object that contains line breaks, then in XML file descriptor (we use the standard TxXMLFileDescriptorsStore, Slide 2.0 Release) the value of the property is correct, i.e., contains line breaks. But when I retrieve the property value as String: String value = descriptor.getProperty(propertyName,namespace).getValue().toString(); it doesn't contain line breaks. For the time being the workaround is to use the URLEncoder/URLDecoder classes. I wonder if the problem can be solved just by means of Slide API. Any help is really appreciated. Yours sincerely, Andrey. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat w/slide not stopping cleanly
I am having exactly same problem with Slide HEAD / Tomcat 5.0.28 / Java 1.4.2 / Linux. shutdown.sh stops Tomcat, but java process is still there, with 10-20 threads. Maybe we should post this into Tomcat group ? Brian Moseley wrote: i'm using the jakarta-slide-server-bin-2.1 binary release for a webapp using slide (but not as the default servlet). the webapp is deployed in tomcat 5.0.28 on os x 10.3.7. when i shutdown tomcat (using `catalina.sh stop'), i see the expected entries in my catalina.out log file, culminating in INFO: Stopping Coyote HTTP/1.1 on http-8080. however, ps reveals the java process still running, and i have to kill the process manually. any ideas what could be causing this problem? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat w/slide not stopping cleanly
Roman D wrote: I am having exactly same problem with Slide HEAD / Tomcat 5.0.28 / Java 1.4.2 / Linux. shutdown.sh stops Tomcat, but java process is still there, with 10-20 threads. Maybe we should post this into Tomcat group ? well, it doesn't happen when slide isn't deployed into tomcat, so i assume it's an issue of slide not shutting down cleanly. i haven't had an opportunity to look into it any further tho. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: role properties not showing up as expected
Michael Smith wrote: one thing i noticed is that the page above seems to be confused about what namespace this property should use. the screenshot which shows the view/modify properties dialog shows the group-member-set property in the slide namespace, but the next screenshot shows the property being set in the DAV namespace. which is correct? It should be in the DAV: namespace. i thought so, but it doesn't look like it is. here's the property that i'm getting in my propfind response: group-member-set xmlns=/group-member-set again, the property definition in Domain.xml (the stock one from slide.war in the jakarta-slide-server-bin-2.1 release) is: revision property name=group-member-set![CDATA[D:href x mlns:D='DAV:'/users/root/D:href]]/property /revision is that a bug? should the property definition include a namespace? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WCK Strange Behavior
Both the reference webdav store and my custom store exhibit the same behavior... I'm using Jetty 5.x on a Mac OS X. Basically the resource properties being returned by Slide do not match what they are in reality. ex. The file 'AmazonLetter.doc' is in the 'files' directory and was last modified on Dec 8th of 2004... Furthermore, if I don't filter from '/files' and I start at the store root - I can never enter into the 'files' directory Request: PROPFIND http://localhost:8080/cansas/AmazonLetter.doc HTTP/1.1 User-Agent: WebDAVFS/1.2.7 (01278000) Darwin/7.7.0 (Power Macintosh) Accept: */* Host: localhost:8080 Content-Type: text/xml Depth: 0 Content-Length: 164 Authorization: Basic YnJpYW46MTIzNDU2 ?xml version=1.0 encoding=utf-8 ? D:propfind xmlns:D=DAV: D:prop D:getlastmodified/ D:getcontentlength/ D:resourcetype/ /D:prop /D:propfind Response: HTTP/1.1 207 Multi Status Date: Wed, 09 Feb 2005 21:32:20 GMT Server: Jetty/5.1.1 (Mac OS X/10.3.7 ppc java/1.4.2_05 Expires: Thu, 01 Jan 1970 00:00:00 GMT Set-Cookie: JSESSIONID=8sbah8bkmts8i;path=/cansas Content-Type: text/xml; charset=UTF-8 Transfer-Encoding: chunked ?xml version=1.0 encoding=UTF-8? D:multistatus xmlns:D=DAV: D:response D:href/cansas/AmazonLetter.doc/D:href D:propstat D:prop D:getlastmodifiedWed, 09 Feb 2005 18:34:20 GMT/D:getlastmodified D:resourcetype D:collection / /D:resourcetype /D:prop D:statusHTTP/1.1 200 OK/D:status /D:propstat D:propstat D:prop D:getcontentlength / /D:prop D:statusHTTP/1.1 404 Not Found/D:status /D:propstat /D:response /D:multistatus Log of my store: 09 Feb 2005 13:32:20 - WebDAV store - INFO - objectExists(String uri) uri [/files/AmazonLetter.doc] root [/Applications/jettyplus/store] 09 Feb 2005 13:32:20 - WebDAV store - INFO - file.exists() [true] 09 Feb 2005 13:32:20 - WebDAV store - INFO - objectExists(String uri) uri [/files/AmazonLetter.doc] root [/Applications/jettyplus/store] 09 Feb 2005 13:32:20 - WebDAV store - INFO - file.exists() [true] 09 Feb 2005 13:32:20 - WebDAV store - INFO - objectExists(String uri) uri [/files/AmazonLetter.doc] root [/Applications/jettyplus/store] 09 Feb 2005 13:32:20 - WebDAV store - INFO - file.exists() [true] 09 Feb 2005 13:32:20 - WebDAV store - INFO - isFolder(String uri) uri [/files/AmazonLetter.doc] root [/Applications/jettyplus/store] 09 Feb 2005 13:32:20 - WebDAV store - INFO - file.isDirectory() [false] 09 Feb 2005 13:32:20 - WebDAV store - INFO - getResourceLength(String uri) uri [/files/AmazonLetter.doc] root [/Applications/jettyplus/store] 09 Feb 2005 13:32:20 - WebDAV store - INFO - file.length() [26624] 09 Feb 2005 13:32:20 - WebDAV store - INFO - getCreationDate(String uri) uri [/files/AmazonLetter.doc] root [/Applications/jettyplus/store] 09 Feb 2005 13:32:20 - WebDAV store - INFO - Date(file.lastModified()) [Wed Dec 08 10:32:16 PST 2004] 09 Feb 2005 13:32:20 - WebDAV store - INFO - getLastModified(String uri) uri [/files/AmazonLetter.doc] root [/Applications/jettyplus/store] 09 Feb 2005 13:32:20 - WebDAV store - INFO - Date(file.lastModified()) [Wed Dec 08 10:32:16 PST 2004] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: role properties not showing up as expected
Brian Moseley wrote: Michael Smith wrote: one thing i noticed is that the page above seems to be confused about what namespace this property should use. the screenshot which shows the view/modify properties dialog shows the group-member-set property in the slide namespace, but the next screenshot shows the property being set in the DAV namespace. which is correct? It should be in the DAV: namespace. i thought so, but it doesn't look like it is. here's the property that i'm getting in my propfind response: group-member-set xmlns=/group-member-set again, the property definition in Domain.xml (the stock one from slide.war in the jakarta-slide-server-bin-2.1 release) is: revision property name=group-member-set![CDATA[D:href x mlns:D='DAV:'/users/root/D:href]]/property /revision is that a bug? should the property definition include a namespace? It looks like a bug - group-member-set is definately defined as being in the DAV: namespace. I wouldn't expect it to work without defining the namespace correctly. Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: versioncontrol-exclude for subfolders
Hi Peter, I didn't excpect it to be that easy ;-) but it works fine Thank you SVen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 09, 2005 5:09 PM To: slide-user@jakarta.apache.org Subject: RE: versioncontrol-exclude for subfolders Hi Sven, please try parameter name=versioncontrol-exclude/slide/files/users;/slide/files/public/pa rameter Regards, Peter -Original Message- From: Sven Pfeiffer [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. Februar 2005 11:48 To: Slide Users Mailing List Subject: RE: versioncontrol-exclude for subfolders it seems like there is another problem. it looks like versioncontrol-exclude is not only for the specified folder, but also for the subfolders. my problem seems to be that i want to set more then one folder to be excluded from version control. it looks like that: /slide/files/users should be excluded /slide/files/publicshould be excluded /slide/files/systemshould be under version control is this possible, or do i have to set auto-version-control to false? thanks in advance SVen -Original Message- From: Sven Pfeiffer [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 09, 2005 11:37 AM To: Slide Users Mailing List (E-mail) Subject: versioncontrol-exclude for subfolders Hi List i want to exclude a folder and all subfolders from versioncontrol. the folder should be a temporary file dump. but if I set parameter name=versioncontrol-exclude/files/temp/parameter and i create a new folder in /files/temp/ lets say /files/temp/first first will be version controlled. is there a possibility to say this folder an all subfolders shouldbe excluded from version control? using * as wildcard doesn't seem to work thanks in advance SVen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ATT: Sven Pfeiffer - file size limitation
Hi Sven, I found the thread in the mailing lists relating to the file size limitation in slide. Were you able to patch this? We are having the same problems as stated in the thread. Your help will be much appreciated. Thank You Clive - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: role properties not showing up as expected
Michael Smith wrote: It looks like a bug - group-member-set is definately defined as being in the DAV: namespace. I wouldn't expect it to work without defining the namespace correctly. well, i can set and get the property by specifying the DAV: namespace, with both cadaver and the client lib, so i guess it all works as it's supposed to. it was just a bit disconcerting to see an empty namespace in the response content, but that's gone now :) thanks for the tips. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Sven Pfeiffer - file size limitation
Hi Clive, I am still trying to find the problem. In the moment I am thinking the problem might be on tomcat-side, which passes the request. But no one in the tomcat mailing lists seems to be able to help me. But development has to go on, so I have to live with the file size limitation of 2 GB for the moment. Whenever I have a little spare time I will try to find the problem and try to fix it. Sorry :-( SVen -Original Message- From: Clive Borrageiro [mailto:[EMAIL PROTECTED] Sent: Thursday, February 10, 2005 8:11 AM To: 'Slide Users Mailing List' Subject: ATT: Sven Pfeiffer - file size limitation Hi Sven, I found the thread in the mailing lists relating to the file size limitation in slide. Were you able to patch this? We are having the same problems as stated in the thread. Your help will be much appreciated. Thank You Clive - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
