Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do I configure Warming Requests avoiding errors 404 on app's log?
    primarykey
    data
    text
    <p>I have enabled <a href="http://code.google.com/intl/it/appengine/docs/python/config/appconfig.html#Warming%20_Requests" rel="nofollow">Warming Requests</a> to my app, adding the following directive in <code>app.yaml</code>.</p> <pre><code>inbound_services: - warmup </code></pre> <p>Looking at app's log I see several entries of this kind:</p> <blockquote> <p>1. 01-05 02:49PM 50.037 /_ah/warmup 404 300ms 280cpu_ms 1kb See details</p> <pre><code>0.1.0.3 - - [05/Jan/2011:05:49:50 -0800] "GET /_ah/warmup HTTP/1.1" 404 1188 </code></pre> <p>2. I 01-05 02:49PM 50.336</p> <p>This request caused a new process to be started for your application,<br> and thus caused your application code to be loaded for the first time.<br> This request may thus take longerand use more CPU than a typical request<br> for your application.</p> </blockquote> <p>This makes sense because the <em>Warming Requests</em> documentation says:</p> <blockquote> <p>This causes the App Engine infrastructure to issue GET requests to /_ah/warmup. You can implement handlers in this directory to perform application-specific tasks, such as pre-caching application data.</p> </blockquote> <p>AFAIK <code>ah</code> is a <a href="http://code.google.com/intl/it/appengine/docs/python/config/appconfig.html#Reserved_URLs" rel="nofollow">reserved URL</a>, i.e. script handler and static file handler paths will never match these paths!</p> <p>Should I simply add the <code>ah/warmup</code> route associating it to an empty web handler for example? Is this correct?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload