headers
Alexandre Clavaud | 1 May 15:39
Picon

Slide on Weblogic with JAAS

Does someone managed to use Slide with JAAS SlideLoginModule for authenticating against users in a Slide
namespace on BEA Weblogic 8 ?

Thanks for help.

----------------------------------------------------
Alexandre Clavaud
Consultant Technique
    ILEM S.A

Tel: +41 79 773 6888
Email : Alexandre.Clavaud <at> ilem.ch
---------------------------------------------------
Permalink | Reply | 0 comments |
headers
Jacob Lund | 2 May 09:02

Re: Non us-ascii character in filenames break. Was: French accent, getting crazy....

I cannot help this - are you sure that you client is using utf8?

I am Danish, and I can store filenames using special Danish letters. I have 
also tested with Russian letter in filenames, and it is working fine!

What you describe sound to me like you client is sending non utf8 encoded 
data to slide, and that will mess up files it the way you describe! Your 
problems are the same as when I tested with windows 2000 and webfolders. 
Windows 2000 only worked when I installed office xp with latest servicepack 
or office 2003. Windows XP seem to be working fine.

DAVExplorer will corrupt filenames if your slide is set to utf8.

If you put a sniffer on you system and monitor the data transmitted between 
client and server, then try following. Upload a file called é.bat and the 
header send from the client should look something like this:

PUT /files/%c3%a9.bat HTTP/1.1
Host: localhost:82

That is: the utf8 escaped version of é is %c3%a9. And the unexcaped utf8 
version of é would be: é. This is correct behavior.

/jacob

----- Original Message ----- 
From: "delbd" <delbd <at> oma.be>
To: "Slide Users Mailing List" <slide-user <at> jakarta.apache.org>
Sent: Friday, April 29, 2005 3:19 PM
Subject: Non us-ascii character in filenames break. Was: French accent,
(Continue reading)

Permalink | Reply | 7 comments |
headers
delbd | 2 May 10:57
Picon

Re: Non us-ascii character in filenames break. Was: French accent, getting crazy....

The put went without a problem. The data is encoded correctly on the database. 
It's an Oracle database and the accents are corrects in it. On propfind, 
slide sends a list of documents with an encoded href. This is the href the 
client should be sending back to slide when it tries any operation on 
document. As detailed in bug report, slide is unable to decode the href it 
has send, this has nothing to do with the client IMO.

For example, a document 
/files/d0_public/téèst.txt
gets a href in the result of  propfind in d0_public like this:
<D:response xmlns:D="DAV:">
  <D:href>/intranet/DAV/files/d0_public/t%C3%A9%C3%A8st.txt</D:href> 
    <D:propstat> 
        <D:prop>
           ...blablabla
however, a GET on this url returns an object not found.
Problem arise wether slide is configured with utf-8 or another charset. I also 
set java.io.encoding to UTF-8 to set the default String encoding to utf-8 
(just to be sure).

See transcript:

delbd <at> CAL-12:~$ telnet localhost 8080
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET /intranet/DAV/files/d0_public/t%C3%A9%C3%A8st.txt HTTP/1.1
Host: localhost:8080

HTTP/1.1 404 Not Found: No object found
(Continue reading)

Permalink | Reply | 6 comments |
headers
Laurent Michenaud | 2 May 12:44
Picon

Problem with the webdav lib and common http client 3.0rc2

I'm trying to use the webdav client lib with the library Jakarta common
http client 3.0rc2.

Most of the methods seem to works well except the propatch method.

My code :

Credentials oCredentiels = new UsernamePasswordCredentials("root",
"root");

HttpClient client = new HttpClient();

client.getState().setCredentials(AuthScope.ANY, oCredentiels);

PropPatchMethod proppatchMethod = new
PropPatchMethod("http://localhost:8080/slide/users/michenux");

proppatchMethod.setDoAuthentication(true);

proppatchMethod.addPropertyToSet("password", "dudule", "S", "slide");

try {

                int state = client.executeMethod(proppatchMethod);

                System.out.println(state);

} catch ( Exception e) {

            e.printStackTrace() ;
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jacob Lund | 2 May 13:20

Re: Non us-ascii character in filenames break. Was: French accent, getting crazy....

I just uploaded a file with that exact name: téèst.txt to my slide version 
2.1.

I tried with both windows explorer webfolder and with my own client - it 
worked fine.

Are you testing with the txfilestore? BTW utf8 is broken in 2.2 so you 
should stay with 2.1 for now.

Also you are showing here - could you verify that the put request from your 
client is also encoding utf8!

My problem is that it works fine in my case - for both filestore and for the 
SQLServer store. This makes me conclude that it is a setup issue or and 
oracle store problem. Or am I missing something?

/jacob

----- Original Message ----- 
From: "delbd" <delbd <at> oma.be>
To: "Slide Users Mailing List" <slide-user <at> jakarta.apache.org>
Sent: Monday, May 02, 2005 10:57 AM
Subject: Re: Non us-ascii character in filenames break. Was: French accent, 
getting crazy....

The put went without a problem. The data is encoded correctly on the 
database.
It's an Oracle database and the accents are corrects in it. On propfind,
slide sends a list of documents with an encoded href. This is the href the
client should be sending back to slide when it tries any operation on
(Continue reading)

Permalink | Reply | 5 comments |
headers
Jacob Lund | 2 May 13:26

Re: Non us-ascii character in filenames break. Was: French accent, getting crazy....

I just noticed something - is the sql scheme for oracle using Unicode?

In order to make SQLServer support utf8 I had to change varchar to 
nvarchar - otherwise it would react in a way similar to what you describe.

If you create a file on you desktop and cut&past some Russian characters 
into the filename and the upload the file to slide, the it will fail unless 
the database supports unicode.

/jacob

----- Original Message ----- 
From: "Jacob Lund" <jl <at> qualiware.net>
To: "Slide Users Mailing List" <slide-user <at> jakarta.apache.org>
Sent: Monday, May 02, 2005 1:20 PM
Subject: Re: Non us-ascii character in filenames break. Was: French accent, 
getting crazy....

>I just uploaded a file with that exact name: téèst.txt to my slide version 
>2.1.
>
> I tried with both windows explorer webfolder and with my own client - it 
> worked fine.
>
> Are you testing with the txfilestore? BTW utf8 is broken in 2.2 so you 
> should stay with 2.1 for now.
>
> Also you are showing here - could you verify that the put request from 
> your client is also encoding utf8!
>
(Continue reading)

Permalink | Reply | 3 comments |
headers
delbd | 2 May 14:25
Picon

Re: Non us-ascii character in filenames break. Was: French accent, getting crazy....

I just tried here. It did this:

---------
delbd <at> CAL-12:~$ telnet localhost 8080
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
PUT /intranet/DAV/files/d0_public/AT%C3%A9%C3%A8st.txt HTTP/1.1
Host: localhost:8080
Cookie: JSESSIONID=8189025AFC93A7C96A797041AA042D01
Authorization: Basic ***hidden ;)***

HTTP/1.1 201 Created
Server: Apache-Coyote/1.1
Pragma: No-cache
Cache-Control: no-cache
Expires: Thu, 01 Jan 1970 01:00:00 CET
ETag: e4f2657596656c1e468fcd473c84cf41
Content-Length: 0
Date: Mon, 02 May 2005 12:09:01 GMT
--------

This should urldecode to/intranet/DAV/files/d0_public/ATéèst.txt and create an 
empty document with that url.

I get this in the tomcat console:
http-8080-Processor24, 02-May-2005 14:18:30, admin, PUT, 201 "Created", 744 
ms, /files/d0_public/AT????st.txt

Then i do a propfind (PROPFIND /intranet/DAV/files/d0_public/ HTTP/1.1) using
(Continue reading)

Permalink | Reply | 0 comments |
headers
delbd | 2 May 14:27
Picon

Re: Non us-ascii character in filenames break. Was: French accent, getting crazy....

Yes oracle database here is configured to use a unicode character set as the 
default charset for all text fields.

Le Lundi 2 Mai 2005 13:26, Jacob Lund a écrit :
> I just noticed something - is the sql scheme for oracle using Unicode?
>
> In order to make SQLServer support utf8 I had to change varchar to
> nvarchar - otherwise it would react in a way similar to what you describe.
>
> If you create a file on you desktop and cut&past some Russian characters
> into the filename and the upload the file to slide, the it will fail unless
> the database supports unicode.
>
> /jacob
>
> ----- Original Message -----
> From: "Jacob Lund" <jl <at> qualiware.net>
> To: "Slide Users Mailing List" <slide-user <at> jakarta.apache.org>
> Sent: Monday, May 02, 2005 1:20 PM
> Subject: Re: Non us-ascii character in filenames break. Was: French accent,
> getting crazy....
>
> >I just uploaded a file with that exact name: téèst.txt to my slide version
> >2.1.
> >
> > I tried with both windows explorer webfolder and with my own client - it
> > worked fine.
> >
> > Are you testing with the txfilestore? BTW utf8 is broken in 2.2 so you
> > should stay with 2.1 for now.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Mark Breitner | 2 May 14:53
Picon
Picon

Trying to change slide WCK folders

Hi,

after installing the WCK I noticed that there are several subfolders like
"files", "hostory" etc.

How do I change this ? How do I create new ones and rename old ones ?

With kind regards

mark Breitner

--

-- 
+++ Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS +++
GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail
Permalink | Reply | 0 comments |
headers
Jacob Lund | 2 May 14:56

Re: Non us-ascii character in filenames break. Was: French accent, getting crazy....

A very quick browsing through google makes me believe that oracle only 
stores unicode if you use nvarchar2 and nclob etc. Even if database is set 
to utf8 in oracle db. Or am I way off?

Could you try to make a search&replace: from VARCHAR2 to NVARCHAR2 and from 
CLOB to NCLOB in the oracle scheme? And then create the database again?

/jacob

----- Original Message ----- 
From: "delbd" <delbd <at> oma.be>
To: "Slide Users Mailing List" <slide-user <at> jakarta.apache.org>
Sent: Monday, May 02, 2005 2:27 PM
Subject: Re: Non us-ascii character in filenames break. Was: French accent, 
getting crazy....

Yes oracle database here is configured to use a unicode character set as the
default charset for all text fields.

Le Lundi 2 Mai 2005 13:26, Jacob Lund a écrit :
> I just noticed something - is the sql scheme for oracle using Unicode?
>
> In order to make SQLServer support utf8 I had to change varchar to
> nvarchar - otherwise it would react in a way similar to what you describe.
>
> If you create a file on you desktop and cut&past some Russian characters
> into the filename and the upload the file to slide, the it will fail 
> unless
> the database supports unicode.
>
(Continue reading)

Permalink | Reply | 1 comment |

Gmane