Done: https://issues.apache.org/jira/browse/WICKET-5873
Regards
Nick
On Mon, Apr 6, 2015 at 12:22 PM, Martin Grigorov
wrote:
> Afaik it didn't break anything in 7.x so I think it is safe to be back
> ported.
> Please file a ticket.
> On Apr 6, 2015 7:20 PM, "Nick Pratt" wrote:
>
> > Any chanc
Afaik it didn't break anything in 7.x so I think it is safe to be back
ported.
Please file a ticket.
On Apr 6, 2015 7:20 PM, "Nick Pratt" wrote:
> Any chance it can be back ported into 6.20 ?
>
>
>
> On Mon, Apr 6, 2015 at 12:17 PM, Martin Grigorov
> wrote:
>
> > We've figured out that some time
Any chance it can be back ported into 6.20 ?
On Mon, Apr 6, 2015 at 12:17 PM, Martin Grigorov
wrote:
> We've figured out that some time ago and removed it for Wicket 7.x.
> On Apr 6, 2015 7:00 PM, "Nick Pratt" wrote:
>
> > OK, now the Wicket cause of this: Why in AbstractResource do we flush
We've figured out that some time ago and removed it for Wicket 7.x.
On Apr 6, 2015 7:00 PM, "Nick Pratt" wrote:
> OK, now the Wicket cause of this: Why in AbstractResource do we flush the
> response after writing the headers (which is invoked from
> setResponseHeaders() )?
> /**
>
> * Flushes th
OK, now the Wicket cause of this: Why in AbstractResource do we flush the
response after writing the headers (which is invoked from
setResponseHeaders() )?
/**
* Flushes the response after setting the headers.
* This is necessary for Firefox if this resource is an image,
* otherwise it messes u
I had a feeling I did, but the problem still remains. Anyway, the
resources served by Wicket are served on a response that is committed
(likely due to a flush() invocation). The Jetty CompressedResponseWrapper
does not compress committed responses:
public ServletOutputStream getOutputStream() th
Hi,
You have asked the same question 2 years ago :-)
http://mail-archives.apache.org/mod_mbox/wicket-users/201211.mbox/%3CCALpvOjtq4=hWkLO=ShUBfG7cZFS+yB-XmWgU+worrgYcTk=+3...@mail.gmail.com%3E
How does the GZipFilter configuration looks like in your web.xml ?
Put a debugger in it and see what h
We've checked all the headers and everything looks fine. The only
difference between whether or not Jetty 9.x gzips the files is whether
Wicket serves the resources. Wicket generated HTML markup is gzipped, as
are all static resources served by Jetty's DefaultServlet. Any .js or .css
files serve
Have you checked that the correct content-type is specified?
We use Jetty8 in a project with Wicket6 and serving package resource
files gzipped works without a problem.
What kind of Packe-Resource-Files do you see not beeing gziped? Can you
share Request/Response headers?
Am 03.04.2015 23:56,
Can resources served from Wicket be gzipped by Jetty's GzipFilter?
We've added the GzipFilter to a simple Quickstart (in front of the
WicketFilter). We can request and receive gzipped files (such as static
.css and .js files) served from Jetty's DefaultServlet, and we see that
.html files served
10 matches
Mail list logo
