You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Joe Hudson <jo...@gmail.com> on 2011/06/17 17:18:59 UTC
is there any way to externalize wicket-event.js
Hi,
I for looking at ways of optimizing a wicket application. And, while
a 304 is returned for wicket-event.js requests, the resource content
is returned as well. Is there any optimizations that can be applied
here? Ideally I would like to host these files (and probably change
their name to have the wicket version) directly through Apache.
I have poked around in the code and all I can see to do is change
HtmlHeaderResolver. But since this is in Application.internalInit I
am hesitant to do so. Any suggestions would be appreciated. Thanks.
Joe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: is there any way to externalize wicket-event.js
Posted by Joe Hudson <jo...@gmail.com>.
Thank you both for your time and attention.
Joe
On Fri, Jun 17, 2011 at 7:15 PM, Chris Colman
<ch...@stepaheadsoftware.com> wrote:
> I'm not sure if this is related to your problem but I see a few server errors relating to the fetching of wicket-event.js and I discovered it's because some agent (crappy browser or crappy bot) is ignoring the case sensitive nature of the .js resource name and making a request with all lowercase letters in path and filename to the web app which then can't locate it because it's doing a case sensitive look up.
>
>>-----Original Message-----
>>From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>>Sent: Saturday, 18 June 2011 1:33 AM
>>To: users@wicket.apache.org
>>Subject: Re: is there any way to externalize wicket-event.js
>>
>>i would figure out why the content is returned with a 304 header.
>>
>>further, when people are looking to optimize these kinds of things
>>they put a caching proxy infront of the app server and tell it to
>>cache js, css, and other staticy files
>>
>>-igor
>>
>>On Fri, Jun 17, 2011 at 8:18 AM, Joe Hudson <jo...@gmail.com> wrote:
>>> Hi,
>>>
>>> I for looking at ways of optimizing a wicket application. And, while
>>> a 304 is returned for wicket-event.js requests, the resource content
>>> is returned as well. Is there any optimizations that can be applied
>>> here? Ideally I would like to host these files (and probably change
>>> their name to have the wicket version) directly through Apache.
>>>
>>> I have poked around in the code and all I can see to do is change
>>> HtmlHeaderResolver. But since this is in Application.internalInit I
>>> am hesitant to do so. Any suggestions would be appreciated. Thanks.
>>>
>>> Joe
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: is there any way to externalize wicket-event.js
Posted by Chris Colman <ch...@stepaheadsoftware.com>.
I'm not sure if this is related to your problem but I see a few server errors relating to the fetching of wicket-event.js and I discovered it's because some agent (crappy browser or crappy bot) is ignoring the case sensitive nature of the .js resource name and making a request with all lowercase letters in path and filename to the web app which then can't locate it because it's doing a case sensitive look up.
>-----Original Message-----
>From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>Sent: Saturday, 18 June 2011 1:33 AM
>To: users@wicket.apache.org
>Subject: Re: is there any way to externalize wicket-event.js
>
>i would figure out why the content is returned with a 304 header.
>
>further, when people are looking to optimize these kinds of things
>they put a caching proxy infront of the app server and tell it to
>cache js, css, and other staticy files
>
>-igor
>
>On Fri, Jun 17, 2011 at 8:18 AM, Joe Hudson <jo...@gmail.com> wrote:
>> Hi,
>>
>> I for looking at ways of optimizing a wicket application. And, while
>> a 304 is returned for wicket-event.js requests, the resource content
>> is returned as well. Is there any optimizations that can be applied
>> here? Ideally I would like to host these files (and probably change
>> their name to have the wicket version) directly through Apache.
>>
>> I have poked around in the code and all I can see to do is change
>> HtmlHeaderResolver. But since this is in Application.internalInit I
>> am hesitant to do so. Any suggestions would be appreciated. Thanks.
>>
>> Joe
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: is there any way to externalize wicket-event.js
Posted by Igor Vaynberg <ig...@gmail.com>.
i would figure out why the content is returned with a 304 header.
further, when people are looking to optimize these kinds of things
they put a caching proxy infront of the app server and tell it to
cache js, css, and other staticy files
-igor
On Fri, Jun 17, 2011 at 8:18 AM, Joe Hudson <jo...@gmail.com> wrote:
> Hi,
>
> I for looking at ways of optimizing a wicket application. And, while
> a 304 is returned for wicket-event.js requests, the resource content
> is returned as well. Is there any optimizations that can be applied
> here? Ideally I would like to host these files (and probably change
> their name to have the wicket version) directly through Apache.
>
> I have poked around in the code and all I can see to do is change
> HtmlHeaderResolver. But since this is in Application.internalInit I
> am hesitant to do so. Any suggestions would be appreciated. Thanks.
>
> Joe
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org