thanks, i realized my mistake, still I can't make it right. Now I'm
doing it like
self.response.headers['Content-Disposition'] = "attachment;
filename*=utf-8 ' ' " + fileinfo.filename.encode('utf-8')
(there are no spaces there, I just added them for better visibility of
single quotes)
trying to follow rfc2184, but obviously I'm missing something. Could
you please tell me what exactly are you putting into this header? If I
can make correct dowloads at least with firefox, that is great
already :)
On 28 окт, 05:24, yejun <[EMAIL PROTECTED]> wrote:
> Check section 4 of rfc 2184. It seems you need to specify the encoding
> type on the value it self, because Content-Disposition itself only
> support us ascii encoding.
>
> http://www.ietf.org/rfc/rfc2183http://www.ietf.org/rfc/rfc2184
>
> On Oct 27, 10:08 pm, Sergey Klevtsov <[EMAIL PROTECTED]> wrote:
>
>
>
> > Well, I tested on 14 files of different types (doc txt zip gif jpg pdf
> > xls). 7 of them, which contained only ascii-characters, were
> > downloaded with Content-Disposition header. 7 other, which included
> > non-ascii (cyrillic, specifically) letters - without the header. So
> > this seems to be the problem (I encoded names with utf-8, have also
> > tried utf-16, but things are even worse then). Well, it's not a very
> > important issue, and it's not urgent for me either, but if this could
> > be fixed easily, that would be great.
>
> > p.s. files I tested on are stil there:http://s-klevzoff.appspot.com/files
>
> > On 27 окт, 20:11, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote:
>
> > > Hi,
>
> > > Can you give an example of the types of filenames with which this is
> > > occurring so I can try to replicate it?
>
> > > We should allow you to set the content-disposition header, so if it's not
> > > being included, it may be that we incorrectly think it's malformed in some
> > > way.
>
> > > -Marzia
>
> > > On Mon, Oct 27, 2008 at 8:50 AM, Sergey Klevtsov <[EMAIL PROTECTED]>wrote:
>
> > > > Ok, I sniffed the traffic between my browser and my app on gae, this
> > > > is what returned on file request:
>
> > > > HTTP/1.1 200 OK
> > > > Cache-Control: no-cache
> > > > Content-Type: application/octet-stream; charset=utf-8
> > > > Date: Mon, 27 Oct 2008 15:39:00 GMT
> > > > Server: Google Frontend
> > > > Content-Length: 2022
>
> > > > Google server deletes Content-Disposition header from response :( but
> > > > only for some files, for example .doc and .txt... GIF files are
> > > > dwonloaded correctly and the header is not deleted. Anyone knows what
> > > > can be done about this?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
