It seems that the 204 error is fixed upon analyzing/fixing the changes made 
at the time the 204 error was occurring.

The cause was the kind of code as below executed in the application's entry 
point.

function setEnv($key, $val){    putenv("$key=$val");    $_ENV[$key] = $val;    
$_SERVER[$key] = $val;}setEnv(CACHE_DRIVER", "memcached");


We are using Lumen Framework.
This was to switch environment for unittest, but the 204 error stopped 
occurring after deleting this.
So far the 204 error was occurring 10 times every 1 minute, but after 
deploying this change we are not seeing the error for about 1 hour.

Not sure if this is a GAE/PHP or Lumen Framework specific bug, but 
reporting just in case it might be helpful for someone.
 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/edc9118d-c0ca-455b-9f96-942fdcd630d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to