It is referring to the root domain having a cookie, in this case, navigating to www.mydomain.com gives a cookie. so this benchmark website is not 100% smart about the fact if cookies are sent with static files.
If you really want to, set up an apache domain to serve static files as like static.mydomain.com, and then use web2py routes to redirect to the correct static subdomain. -- Thadeus On Thu, Oct 28, 2010 at 8:51 AM, annet <annet.verm...@gmail.com> wrote: > You mean in a production environment I should not serve static files > from the apps static folder? What happens to the dynamic URLs in that > case? > > At the moment I edit the static files within web2py, and I quite like > the 'pack all' and 'upload and install packed application' features to > deploy an application. If I'd move all the static files to Apache, > deploying an application would become more complicated, wouldn't it. > > BTW I tested the performance of my application here: > http://groups.google.com/group/web2py/browse_thread/thread/da47638dbc515735 > Does anyone of you get the same remarks about cookieless domains? > > > Kind regards, > > Annet. >
