Hi After upgrading from wicket 1.2.6 to 1.3 we got a problem with opening PDF files inline in a browser window. At least for some browser versions and/or PDF readers, it now opens the PDF file in a separate window instead of inline.
The difference is that in Wicket 1.3 ";charset=UTF-8" is always appended to the content type. If ResourceState::getContentType() returns "application/pdf", this is what I see in a HTTP debugger: Wicket 1.2.6: Content-Type: application/pdf Wicket 1.3.1: Content-Type: application/pdf; charset=UTF-8 The ";charset=UTF-8" is appended in ResourceStreamRequestTarget, and I can't see a way to override it. Any suggestions how to fix this? Niels -- View this message in context: http://www.nabble.com/Problem-with-opening-inline-PDF-file-due-to-%22-charset%3DUTF-8%22-in-content-type-tp15757124p15757124.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
