Re: Tomcat 4 vs Tomcat 5 and MIME settings
Stephen Thomas wrote:
Does this mean it will still return a charset? I don't need any charset
returned.
Now, you won't get the charset unless you ask for it (so no more
Content-Type: image/gif; charset=iso-8859-1
). However, if you call response.setCharacterEncoding("iso-9959-1"),
you now get it in the response.
I will continue using Tomcat 4.1.27 until the fixed release of 5 is stable.
Will be released soon.
-- Jeanfrancois
Thanks,
Steve
-Original Message-
From: Jeanfrancois Arcand [mailto:[EMAIL PROTECTED]
Sent: 01 December 2003 17:54
To: Tomcat Users List
Subject: Re: Tomcat 4 vs Tomcat 5 and MIME settings
Bill Barker has already fixed this:
org.apache.coyote.Response
revision 1.31
date: 2003/11/16 05:20:23; author: billbarker; state: Exp; lines: +10 -3
Restore the ability to explicitly set the charset to iso-latin-1.
Download the latest Tomcat 5 source and try it.
-- Jeanfrancois
Stephen Thomas wrote:
Hi,
I must apologise, I've never used these types of systems before and have
sent this email to a couple of addresses.
I am a developer of Voice applications. I use the Tomcat servlet engine to
host my applications which are then fetched from the voice server. I am
currently having an issue with Tomcat 5 and 'content-type'. The voice
server
can play .vox files and I fetch such a file from Tomcat 5 and get the
following header:
lwp-request -d -e http://10.100.1.113:8080/test/soxTest1.vox
Connection: close
Date: Mon, 01 Dec 2003 09:30:03 GMT
Server: Apache-Coyote/1.1
Content-Length: 8130
Content-Type: audio/x-vox;charset=ISO-8859-1
ETag: W/"8130-1069965466970"
Last-Modified: Thu, 27 Nov 2003 20:37:46 GMT
Client-Date: Mon, 01 Dec 2003 09:29:38 GMT
Client-Peer: 10.100.1.113:8080
I have added the following lines to web.xml
vox
audio/x-vox
The file fails to play because of the charset being appended to the
'content-type'. When I host the application and .vox file on Tomcat 4 I can
play the file as the content-type is returned as only 'audio/x-vox'.
Please could you help me as I'd rather use Tomcat 5 but this issue is
currently stopping me.
Thanks in advance,
Steve
-
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]
RE: Tomcat 4 vs Tomcat 5 and MIME settings
Does this mean it will still return a charset? I don't need any charset returned. I will continue using Tomcat 4.1.27 until the fixed release of 5 is stable. Thanks, Steve -Original Message- From: Jeanfrancois Arcand [mailto:[EMAIL PROTECTED] Sent: 01 December 2003 17:54 To: Tomcat Users List Subject: Re: Tomcat 4 vs Tomcat 5 and MIME settings Bill Barker has already fixed this: org.apache.coyote.Response revision 1.31 date: 2003/11/16 05:20:23; author: billbarker; state: Exp; lines: +10 -3 Restore the ability to explicitly set the charset to iso-latin-1. Download the latest Tomcat 5 source and try it. -- Jeanfrancois Stephen Thomas wrote: >Hi, > >I must apologise, I've never used these types of systems before and have >sent this email to a couple of addresses. > >I am a developer of Voice applications. I use the Tomcat servlet engine to >host my applications which are then fetched from the voice server. I am >currently having an issue with Tomcat 5 and 'content-type'. The voice server >can play .vox files and I fetch such a file from Tomcat 5 and get the >following header: > >lwp-request -d -e http://10.100.1.113:8080/test/soxTest1.vox >Connection: close >Date: Mon, 01 Dec 2003 09:30:03 GMT >Server: Apache-Coyote/1.1 >Content-Length: 8130 >Content-Type: audio/x-vox;charset=ISO-8859-1 >ETag: W/"8130-1069965466970" >Last-Modified: Thu, 27 Nov 2003 20:37:46 GMT >Client-Date: Mon, 01 Dec 2003 09:29:38 GMT >Client-Peer: 10.100.1.113:8080 > >I have added the following lines to web.xml > >vox >audio/x-vox > > >The file fails to play because of the charset being appended to the >'content-type'. When I host the application and .vox file on Tomcat 4 I can >play the file as the content-type is returned as only 'audio/x-vox'. > >Please could you help me as I'd rather use Tomcat 5 but this issue is >currently stopping me. > >Thanks in advance, > >Steve > > >- >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: Tomcat 4 vs Tomcat 5 and MIME settings
Bill Barker has already fixed this: org.apache.coyote.Response revision 1.31 date: 2003/11/16 05:20:23; author: billbarker; state: Exp; lines: +10 -3 Restore the ability to explicitly set the charset to iso-latin-1. Download the latest Tomcat 5 source and try it. -- Jeanfrancois Stephen Thomas wrote: Hi, I must apologise, I've never used these types of systems before and have sent this email to a couple of addresses. I am a developer of Voice applications. I use the Tomcat servlet engine to host my applications which are then fetched from the voice server. I am currently having an issue with Tomcat 5 and 'content-type'. The voice server can play .vox files and I fetch such a file from Tomcat 5 and get the following header: lwp-request -d -e http://10.100.1.113:8080/test/soxTest1.vox Connection: close Date: Mon, 01 Dec 2003 09:30:03 GMT Server: Apache-Coyote/1.1 Content-Length: 8130 Content-Type: audio/x-vox;charset=ISO-8859-1 ETag: W/"8130-1069965466970" Last-Modified: Thu, 27 Nov 2003 20:37:46 GMT Client-Date: Mon, 01 Dec 2003 09:29:38 GMT Client-Peer: 10.100.1.113:8080 I have added the following lines to web.xml vox audio/x-vox The file fails to play because of the charset being appended to the 'content-type'. When I host the application and .vox file on Tomcat 4 I can play the file as the content-type is returned as only 'audio/x-vox'. Please could you help me as I'd rather use Tomcat 5 but this issue is currently stopping me. Thanks in advance, Steve - 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]
Tomcat 4 vs Tomcat 5 and MIME settings
Hi, I must apologise, I've never used these types of systems before and have sent this email to a couple of addresses. I am a developer of Voice applications. I use the Tomcat servlet engine to host my applications which are then fetched from the voice server. I am currently having an issue with Tomcat 5 and 'content-type'. The voice server can play .vox files and I fetch such a file from Tomcat 5 and get the following header: lwp-request -d -e http://10.100.1.113:8080/test/soxTest1.vox Connection: close Date: Mon, 01 Dec 2003 09:30:03 GMT Server: Apache-Coyote/1.1 Content-Length: 8130 Content-Type: audio/x-vox;charset=ISO-8859-1 ETag: W/"8130-1069965466970" Last-Modified: Thu, 27 Nov 2003 20:37:46 GMT Client-Date: Mon, 01 Dec 2003 09:29:38 GMT Client-Peer: 10.100.1.113:8080 I have added the following lines to web.xml vox audio/x-vox The file fails to play because of the charset being appended to the 'content-type'. When I host the application and .vox file on Tomcat 4 I can play the file as the content-type is returned as only 'audio/x-vox'. Please could you help me as I'd rather use Tomcat 5 but this issue is currently stopping me. Thanks in advance, Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
