Re: [Resin-interest] Quercus and gallery 2.1
Hi, Well, it doesn't work with the latest bersion of gallery either. Anything i can do to help track it down let me know Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sam Sent: 21 May 2007 18:22 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] Quercus and gallery 2.1 Anyone running gallery2.1 successfully with resin-pro-3.1.1 I had gallery 2.1 running successfully on a pre 3.1.1 release of 3.1. Having upgraded to 3..1 I now get loads of usr/web/databases/webapps/gallery2/modules/core/classes/Gallery.class:60 7: Warning: Assertion !empty($key) failed Bug report here: http://bugs.caucho.com/view.php?id=1744 It may be that this is really a bug in gallery, perhaps the assertion should not be failing. Prior to 3.1.1, Quercus did not evaluate assert expressions. Of course, it could also be a bug in Quercus, a bug that causes the $key to be empty when it should not be. -- Sam ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest* To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html *___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] 304 status
On May 18, 2007, at 5:02 AM, Alex Sharaz wrote: Other times I get the 304 status code. We've got random occurrences where setting a browser to auto detect proxy settings doesn't work and i'm wondering if these occurrences could coincide with the 304 status codes I can see in the logs. I suppose the question is. Can i reconfigure something to get rid of the 304 entries in the logs? I'm a little confused. I can add a bug report to allow filtering of 304 in the logs, but I'm not sure if there's another issue you're reporting. -- Scott Alex -Original Message- From: [EMAIL PROTECTED] [mailto:resin-interest- [EMAIL PROTECTED] On Behalf Of Scott Ferguson Sent: 17 May 2007 18:45 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] 304 status On May 17, 2007, at 10:02 AM, Jean-Francois Lamy wrote: I am trying to understand how resin, apache and proxies interact with respect to caching. I have a jsp page which is meant to be always dynamic; headers are used to prevent it from being cached. However, the page loads js, css, and various images, which I would like to be cached. Currently, the browser (IE7) requests those items, and Resin returns 304 (up-to-date) status. The browser is NOT set to force request at each page. This generates a lot of requests, which are painful when going through proxies. What are the headers for the JSP page? With no caching headers, Resin doesn't cache at all, i.e. no-cache is the default. So the 304 is strange, unless the headers are telling Resin to cache. (Serge's recommendations are good ones for general understanding of HTTP caching, but the described behavior seems odd.) -- Scott Is there a recipe for forcing the JSP to always reload (my JSPs are served through a dispatching servlet which does an include, and therefore servlet is able manipulate the headers), and yet let the browser know that the js and css it has in cache are just fine ? Jean-François Lamy Technologies Teximus inc. www.teximus.com +1 514.878.1577 (Canada) +33(0) 8.70.44.49.02 (Europe) ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin- interest** *** To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html ** ***___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] 304 status
Sorry didn't phrase that properly. If a client makes a request for wpad.dat, is there any way of always returning a copy of the file instead of an http status 304 message? Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ferguson Sent: 22 May 2007 16:49 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] 304 status On May 18, 2007, at 5:02 AM, Alex Sharaz wrote: Other times I get the 304 status code. We've got random occurrences where setting a browser to auto detect proxy settings doesn't work and i'm wondering if these occurrences could coincide with the 304 status codes I can see in the logs. I suppose the question is. Can i reconfigure something to get rid of the 304 entries in the logs? I'm a little confused. I can add a bug report to allow filtering of 304 in the logs, but I'm not sure if there's another issue you're reporting. -- Scott Alex -Original Message- From: [EMAIL PROTECTED] [mailto:resin-interest- [EMAIL PROTECTED] On Behalf Of Scott Ferguson Sent: 17 May 2007 18:45 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] 304 status On May 17, 2007, at 10:02 AM, Jean-Francois Lamy wrote: I am trying to understand how resin, apache and proxies interact with respect to caching. I have a jsp page which is meant to be always dynamic; headers are used to prevent it from being cached. However, the page loads js, css, and various images, which I would like to be cached. Currently, the browser (IE7) requests those items, and Resin returns 304 (up-to-date) status. The browser is NOT set to force request at each page. This generates a lot of requests, which are painful when going through proxies. What are the headers for the JSP page? With no caching headers, Resin doesn't cache at all, i.e. no-cache is the default. So the 304 is strange, unless the headers are telling Resin to cache. (Serge's recommendations are good ones for general understanding of HTTP caching, but the described behavior seems odd.) -- Scott Is there a recipe for forcing the JSP to always reload (my JSPs are served through a dispatching servlet which does an include, and therefore servlet is able manipulate the headers), and yet let the browser know that the js and css it has in cache are just fine ? Jean-François Lamy Technologies Teximus inc. www.teximus.com +1 514.878.1577 (Canada) +33(0) 8.70.44.49.02 (Europe) ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin- interest** *** To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html ** ***___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest* To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html *___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] 304 status
o.k. fair enough doesn't matter then many thanks alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ferguson Sent: 22 May 2007 17:11 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] 304 status On May 22, 2007, at 8:59 AM, Alex Sharaz wrote: Sorry didn't phrase that properly. If a client makes a request for wpad.dat, is there any way of always returning a copy of the file instead of an http status 304 message? The 304 is a response requested by the client, i.e. the client sends If-Modified-Since or If-None-Match headers. If the wpad.dat hasn't changed, a caching-header-aware servlet will return a 304 instead of the data. Resin's FileServlet understands those headers, so will return a 304 if the file hasn't changed. -- Scott Alex -Original Message- From: [EMAIL PROTECTED] [mailto:resin-interest- [EMAIL PROTECTED] On Behalf Of Scott Ferguson Sent: 22 May 2007 16:49 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] 304 status On May 18, 2007, at 5:02 AM, Alex Sharaz wrote: Other times I get the 304 status code. We've got random occurrences where setting a browser to auto detect proxy settings doesn't work and i'm wondering if these occurrences could coincide with the 304 status codes I can see in the logs. I suppose the question is. Can i reconfigure something to get rid of the 304 entries in the logs? I'm a little confused. I can add a bug report to allow filtering of 304 in the logs, but I'm not sure if there's another issue you're reporting. -- Scott Alex -Original Message- From: [EMAIL PROTECTED] [mailto:resin-interest- [EMAIL PROTECTED] On Behalf Of Scott Ferguson Sent: 17 May 2007 18:45 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] 304 status On May 17, 2007, at 10:02 AM, Jean-Francois Lamy wrote: I am trying to understand how resin, apache and proxies interact with respect to caching. I have a jsp page which is meant to be always dynamic; headers are used to prevent it from being cached. However, the page loads js, css, and various images, which I would like to be cached. Currently, the browser (IE7) requests those items, and Resin returns 304 (up-to-date) status. The browser is NOT set to force request at each page. This generates a lot of requests, which are painful when going through proxies. What are the headers for the JSP page? With no caching headers, Resin doesn't cache at all, i.e. no-cache is the default. So the 304 is strange, unless the headers are telling Resin to cache. (Serge's recommendations are good ones for general understanding of HTTP caching, but the described behavior seems odd.) -- Scott Is there a recipe for forcing the JSP to always reload (my JSPs are served through a dispatching servlet which does an include, and therefore servlet is able manipulate the headers), and yet let the browser know that the js and css it has in cache are just fine ? Jean-François Lamy Technologies Teximus inc. www.teximus.com +1 514.878.1577 (Canada) +33(0) 8.70.44.49.02 (Europe) ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin- interest* * *** To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html * * ***___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin- interest** *** To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html ** ***___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest* To view the terms under which this email is
[Resin-interest] request: for openads comp on quercus
Hi, Just wanted to respectfully request compatibility assurance for openads. I'm having trouble getting through the database tables creations phase of the install and I'm not getting any error messages. Since it's a popular ad server I thought I'd just put that out there. thanks, atomi ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] request: for openads comp on quercus
On May 22, 2007, at 11:33 AM, atomi wrote: Hi, Just wanted to respectfully request compatibility assurance for openads. Thanks. I've just added a bug report: http://bugs.caucho.com/ view.php?id=1753 -- Scott I'm having trouble getting through the database tables creations phase of the install and I'm not getting any error messages. Since it's a popular ad server I thought I'd just put that out there. thanks, atomi ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest