DO NOT REPLY [Bug 24504] - Cannot create a document that has accent characters (Latin) in it's name

2003-11-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504

Cannot create a document that has accent characters (Latin) in it's name





--- Additional Comments From [EMAIL PROTECTED]  2003-11-18 16:34 ---
Hi Oleg.

Yes, I'am using a multipart post.

In our application we want to upload files to a file server from a java 
application via HTTP.  We use multipart because we have to include extra 
information for the server application to be able to handle the data (ie : link 
the file to a database object etc ...).  We also want to be able to upload 
multiple files (wichi works well as long as we have no accent in the filenames)

--
Here is the code that buids the file parts

HttpClient client = new HttpClient();
MultipartPostMethod httpsPost = new MultipartPostMethod ( m_docServer );

//Set header information
httpsPost.setRequestHeader(Content-Type, multipart/form-data; 
boundary=+BOUNDS);

//Adding the main parts.
StringPart partToAdd = new StringPart(ClassUID, classUID);
partToAdd.setTransferEncoding(null);
partToAdd.setContentType(null);
httpsPost.addPart( partToAdd );

partToAdd = new StringPart(MethodName, methodName);
partToAdd.setTransferEncoding(null);
partToAdd.setContentType(null);
httpsPost.addPart( partToAdd );

partToAdd = new StringPart(Params, params);
partToAdd.setTransferEncoding(null);
partToAdd.setContentType(null);
httpsPost.addPart( partToAdd );


//Adding teh files parts.
int i=0;
Iterator iterator = parts.keySet().iterator();
AI_DOCPART part;
String partID;
String partFile;
FilePart fPart;

//loop until we have created all file parts.
while(iterator.hasNext()){
  part = (AI_DOCPART)(iterator.next());
  partID= part.getIDAsString();
  partFile = (String) parts.get(part);
  try {
fPart = new FilePart(FILE+(i+1), new File(partFile));
//partToAdd.setContentType(null);
//partToAdd.setTransferEncoding( null );
httpsPost.addPart(fPart);
  }
  catch (FileNotFoundException e) {
  throw new AIException(ERR_INVALIDE_FILENAME,,GUIMediator.getStringResource
(Corporate,ERR_INVALIDE_FILENAME),);
  }
  partToAdd = new StringPart(PARTNUMBER+(i+1) , partID);
  partToAdd.setContentType(null);
  partToAdd.setTransferEncoding( null );
  httpsPost.addPart( partToAdd );   
  i++;  
}

//Set timeout in Milliseconds - 30 secondes
client.setConnectionTimeout( 3 );

//Send the data
int status=0;
try {
status = client.executeMethod(httpsPost);
}
...

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 24504] - Cannot create a document that has accent characters (Latin) in it's name

2003-11-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504

Cannot create a document that has accent characters (Latin) in it's name





--- Additional Comments From [EMAIL PROTECTED]  2003-11-18 17:30 ---
Form-based File Upload in HTML specification (RFC 1867)
http://www.ietf.org/rfc/rfc1867.txt that HttpClient implements follows the
rules of all multipart MIME data streams as outlined in RFC 1521 and RFC 1522.
MIME specification requires all non-ASCII content to be represented using ASCII
charset only. Currently HttpClient does not perform such translation
automatically. You will have to take care of filename encoding prior to passing
it to the FilePart as a parameter.

I was going to contribute quote-printable encoder/decoder to the Commons Codec
library but never got a chance.

To sum things up: if the relevant RFCs are to be strictly adhered to, the
behaviour on the part of HttpClient is correct. However, I do agree that it
would be nice if HttpClient took care of non-ASCII charset translation
automatically. So, feel free to reopen this bug as a feature request.

Oleg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 24504] - Cannot create a document that has accent characters (Latin) in it's name

2003-11-14 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504

Cannot create a document that has accent characters (Latin) in it's name





--- Additional Comments From [EMAIL PROTECTED]  2003-11-14 08:58 ---
Eric,
Are you using MultipartPostMethod by any chance? Please give me a bit more
details about what your application is supposed to do and what you are trying to
accomplish, so I would not have to play a private detective.

Oleg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 24504] - Cannot create a document that has accent characters (Latin) in it's name

2003-11-13 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504

Cannot create a document that has accent characters (Latin) in it's name

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 24504] - Cannot create a document that has accent characters (Latin) in it's name

2003-11-13 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504

Cannot create a document that has accent characters (Latin) in it's name





--- Additional Comments From [EMAIL PROTECTED]  2003-11-14 00:36 ---

My fault, by document I was refering to file (physical file onthe hard drive)
ie : c:\work\DocumentDeTèst.txt  -- This filename has an accent.


I am using the latest version : 2.0 Rc2

As to getAsciiBytes method, as its name implies it is supposed to return ASCII
characters only. So, the behaviour of the method is correct.

Precisly, but because of that the accent based charaters are converted to ?
ie : c:\work\DocumentDeTèst.txt -- c:\work\DocumentDeT?st.txt

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 24504] - Cannot create a document that has accent characters (Latin) in it's name

2003-11-08 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24504

Cannot create a document that has accent characters (Latin) in it's name





--- Additional Comments From [EMAIL PROTECTED]  2003-11-08 11:29 ---
Eric,
My apologies, but I do not quite understand the nature of the problem. What do
you mean by 'cannot create a document'? What do you mean by a document in the
first place? Request content body? Response content body?

what version of HttpClient are you using and what is it you are trying to get done?

As to getAsciiBytes method, as its name implies it is supposed to return ASCII
characters only. So, the behaviour of the method is correct.

You might want to have a look at the HttpClient character encoding guide for
more details:

http://jakarta.apache.org/commons/httpclient/charencodings.html

I'll have no choice but to mark the report as invalid unless more information is
given

Oleg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]