Bad encoding of streamed CSV with Stripes / Tomcat

Actually i'm trying to stream a CSV file. I set the encoding to windows-1252 but it seems it is still streamed as UTF-8 file.

   final String encoding = "windows-1252";
   exportResolution = new StreamingResolution(builder.getContentType() + ";charset=" + encoding.toLowerCase()) {
        @Override
        public void stream(HttpServletResponse response) throws Exception {
            // Set response headers
            response.setHeader("Cache-control", "private, max-age=0");
            response.setCharacterEncoding(encoding);
            OutputStream os = response.getO开发者_开发知识库utputStream();
            writeExportStream(os,builder);
        }
    }.setFilename(filename);

writeExportStream just streams the content to the outputstream (with pagination and db calls, it takes some time)

It doesn't work in local (jetty plugin) + dev (tomcat) Neither with firefox / chrome

I've not tested but people at work told me that it works better when we don't stream the content but we write the file in one time after having loaded all the objets we want from db.

Anybody know what is happening? Thanks

Btw my headers:

HTTP/1.1 200 OK
Content-Language: fr-FR
Content-Type: text/csv;charset=windows-1252
Content-Disposition: attachment;filename="export_rshop_01-02-11.csv"
Cache-Control: private, max-age=0
Transfer-Encoding: chunked
Server: Jetty(6.1.14)

I want the file to be able to be imported in excel in windows-1252 but i can't, it just open in utf8 while my header is windows-1252

---

The problem lies in the writeExportStream(os,builder); method. We can't see what encoding operations it is performing, but I'm guessing it is writing UTF-8 data.

---

The output operation needs to perform two encoding tasks:

1. Tell the client what encoding the response text is in (via the headers)
2. Encode the data writen to the client in a matching encoding (e.g. via a writer)

Step 1 is being done correctly. Step 2 is probably the source of the error.

If you use the provided writer, it will encode character data in the appropriate response encoding.

If pre-encoded data is written via the raw byte stream (getOutputStream()), you need to make sure this process uses the same encoding.