jmathai / epiphany

A micro PHP framework that's fast, easy, clean and RESTful. The framework does not do a lot of magic under the hood. It is, by design, very simple and very powerful.
https://github.com/jmathai/epiphany
Other
686 stars 139 forks source link

Unknown notices #71

Closed cr1st1an closed 11 years ago

cr1st1an commented 11 years ago

Hi Jaisen,

I've been seeing a weird notice in my logs, and not sure what's wrong and/or if requests to such routes are being lost. Could you give me some pointers?

Thanks, Cris

URLS on this sample: http://tic.mx/t82 & http://tic.mx/t83

////// LOG

2013/09/12 16:26:22 [error] 7323#0: *137347 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 184.72.6.38, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx"


2013/09/12 16:26:22 [error] 7323#0: 137345 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 184.72.6.38, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 16:26:22 [error] 7323#0: 137353 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 109.68.166.9, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 16:26:49 [error] 7323#0: 137372 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 98.137.207.35, server: tic.mx, request: "HEAD /t82 HTTP/1.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 16:26:54 [error] 7323#0: 137382 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 50.57.227.76, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 16:27:49 [error] 7323#0: 137404 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 23.29.122.195, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 16:28:11 [error] 7323#0: 137408 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 37.59.18.44, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 16:28:20 [error] 7323#0: 137412 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 37.59.16.202, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 16:37:56 [error] 7323#0: 137450 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 184.72.22.246, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 16:38:00 [error] 7323#0: 137454 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 54.246.137.243, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 16:42:32 [error] 7323#0: 137474 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 50.56.221.75, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 16:45:01 [error] 7323#0: 137493 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 184.72.80.237, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 16:55:07 [error] 7323#0: 137552 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 50.18.8.79, server: tic.mx, request: "HEAD /t82 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 18:52:47 [error] 7323#0: 138146 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 54.246.137.243, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 18:52:47 [error] 7323#0: 138152 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 184.72.6.38, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 18:52:47 [error] 7323#0: 138154 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 184.72.6.38, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 18:52:48 [error] 7323#0: 138156 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 108.166.55.48, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 18:52:53 [error] 7323#0: 138169 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 98.137.207.35, server: tic.mx, request: "HEAD /t83 HTTP/1.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 18:56:36 [error] 7323#0: 138239 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 69.171.248.7, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 18:58:59 [error] 7323#0: 138261 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 37.59.16.202, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:04:57 [error] 7323#0: 138341 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 50.56.209.28, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:06:13 [error] 7323#0: 138353 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 54.219.1.64, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:10:01 [error] 7323#0: 138369 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 37.59.16.156, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:20:14 [error] 7323#0: 138411 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 23.29.122.203, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:20:14 [error] 7323#0: 138417 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 23.29.122.203, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:20:14 [error] 7323#0: 138421 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 98.137.207.35, server: tic.mx, request: "HEAD /t83 HTTP/1.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:23:37 [error] 7323#0: 138476 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 50.18.8.79, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:28:54 [error] 7323#0: 138518 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 23.29.122.222, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:28:55 [error] 7323#0: 138521 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 140.109.21.210, server: tic.mx, request: "HEAD /t83 HTTP/1.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:28:59 [error] 7323#0: 138530 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 37.59.16.161, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:30:02 [error] 7323#0: 138545 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 37.59.16.154, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:30:18 [error] 7323#0: 138543 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 37.59.16.223, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:30:52 [error] 7323#0: 138570 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 37.59.18.35, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:30:52 [error] 7323#0: 138572 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 37.59.18.41, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 19:36:28 [error] 7323#0: 138606 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 50.56.221.75, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 20:20:28 [error] 7323#0: 138892 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 184.72.6.38, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 20:20:28 [error] 7323#0: 138894 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 184.72.6.38, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 20:20:42 [error] 7323#0: 138901 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 176.34.78.244, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 20:21:17 [error] 7323#0: 138909 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 23.29.122.222, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx" 2013/09/12 20:38:58 [error] 7323#0: *139050 FastCGI sent in stderr: "PHP message: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /srv/vhosts/tic.mx/vendors/epi/EpiRoute.php on line 133" while reading response header from upstream, client: 37.59.16.221, server: tic.mx, request: "HEAD /t83 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tic.mx"

georules commented 11 years ago

Seems to me that you've made a route attempt to call a function that doesn't exist. Is there an easy way for you test all of your routes?

cr1st1an commented 11 years ago

These are all my routes, the weird thing is that the url works fine, the only way I can see the warning is through the logs, and it doesn't happen on all the requests...

/* TIC */
getApi()->get('/', array('Route_Posts', 'getRecent'), EpiApi::external);
getApi()->get('/anuncios/(.*)', array('Route_Posts', 'getRoot'), EpiApi::external);
getApi()->get('/anuncio/editar', array('Route_Posts', 'getStepOne'), EpiApi::external);
getApi()->get('/id/(.*)', array('Route_Profiles', 'getProfile'), EpiApi::external);
getApi()->get('/nuevo', array('Route_Static', 'getNew'), EpiApi::external);
getApi()->get('/off', array('Route_Sessions', 'getOff'), EpiApi::external);
getApi()->get('/on', array('Route_Sessions', 'getRoot'), EpiApi::external);
getApi()->get('/on_manage_pages', array('Route_Sessions', 'getAccounts'), EpiApi::external);
getApi()->get('/opciones', array('Route_Profiles', 'getSettings'), EpiApi::external);
getApi()->get('/t(.*)', array('Route_Posts', 'getPost'), EpiApi::external);

getApi()->post('/p1', array('Route_Posts', 'postStepOne'), EpiApi::external);
getApi()->post('/p2', array('Route_Posts', 'postStepTwo'), EpiApi::external);

/* SERVICES */
getApi()->get('/sitemap.xml', array('Route_Services', 'getSitemap'), EpiApi::external);
getApi()->post('/mandrill', array('Route_Services', 'postMandrill'), EpiApi::external);

/* DEFAULT */
getApi()->get('(.*)', array('Route_Static', 'error404'), EpiApi::external);
getApi()->post('(.*)', array('Route_Static', 'error404'), EpiApi::external);
getApi()->delete('(.*)', array('Route_Static', 'error404'), EpiApi::external);
getApi()->put('(.*)', array('Route_Static', 'error404'), EpiApi::external);
cr1st1an commented 11 years ago

Also, it happens randomly on different routes, not only on '/t(.*)'

georules commented 11 years ago

If you could somehow log the data before the call on line 133 in EpiRoute.php, it might help you get an idea of what information is not being set properly. The requests are not working intermittently?

cr1st1an commented 11 years ago

I'll try to do that, I haven't experienced any issues, I don't know if it's a warning that doesn't break functionality or something that prevents some people to see the app. Will keep an eye on it!

jmathai commented 11 years ago

I normally see this error when the class/method defined in the route doesn't.

On Thu, Sep 12, 2013 at 5:46 PM, Cristian Castillo <notifications@github.com

wrote:

I'll try to do that, I haven't experienced any issues, I don't know if it's a warning that doesn't break functionality or something that prevents some people to see the app. Will keep an eye on it!

— Reply to this email directly or view it on GitHubhttps://github.com/jmathai/epiphany/issues/71#issuecomment-24366349 .

cr1st1an commented 11 years ago

doesn't?

jmathai commented 11 years ago

Doesn't exist :)

cr1st1an commented 11 years ago

I see on the example that the methods are defined 'static public function' while mine are just 'public function' could this be an issue?

jmathai commented 11 years ago

Shouldn't be the problem.

Do you know if an exception is being thrown? https://github.com/jmathai/epiphany/blob/master/src/EpiRoute.php#L194

Also, could you enable debugging and paste in what that gives you? https://github.com/jmathai/epiphany/blob/master/examples/debug/index.php

cr1st1an commented 11 years ago

The thing is that it works just fine for me, and nobody has reported any issues, just that I see it in the logs and don't know if the user sees something and doesn't tell or if it just works as expected.

jmathai commented 11 years ago

Ah. These are HEAD requests. You can replicate it by doing this and reproduce the log entries.

curl -I http://tic.mx/t83

So...end users shouldn't be seeing errors. Not sure what's making the HEAD requests.

[edit: clarified that end users shouldn't be seeing errors]

cr1st1an commented 11 years ago

Yep, that did it... I'm almost sure it has to do with twitter cards, is there a way for the 'head request' to return the 'get' content, or am I mixing concepts?

Thanks! Cris

jmathai commented 11 years ago

I don't believe there's HEAD support in the routes module (though it's trivial to add).

You don't want to return the body of the request for a HEAD request but I think it's a valid issue to create that HEAD requests would return the endpoint's GET handler minus the body. Feel free to open that issue. And if you feel inclined to tackle fixing it it's a good way to get under the hood of the routes module :).

http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html

9.4 HEAD

The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request SHOULD be identical to the information sent in response to a GET request. This method can be used for obtaining metainformation about the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext links for validity, accessibility, and recent modification.

The response to a HEAD request MAY be cacheable in the sense that the information contained in the response MAY be used to update a previously cached entity from that resource. If the new field values indicate that the cached entity differs from the current entity (as would be indicated by a change in Content-Length, Content-MD5, ETag or Last-Modified), then the cache MUST treat the cache entry as stale.

cr1st1an commented 11 years ago

Cool, will open the issue and will try to tackle it next week. Thanks!

jmathai commented 11 years ago

Sorry, had to do it :).

https://github.com/jmathai/epiphany/commit/622d2c545737a5871be93a03cc0a7698a80c5299

cr1st1an commented 11 years ago

Even better! Also, remember the memcache issue, where you couldn't set the Session like this:

EpiSession::employ(
        array(
            EpiSession::MEMCACHED,
            getConfig()->get('memcached')->host,
            getConfig()->get('memcached')->port,
            getConfig()->get('memcached')->compress,
            getConfig()->get('memcached')->expiry
        )
);

Looks like the Cache has the same issue, I've been having to set it like this in EpiCache_Memcached.php

    public function __construct($params = array()) {
        $this->host = !empty($params[0]) ? $params[0] : getConfig()->get('memcached')->host;
        $this->port = !empty($params[1]) ? $params[1] : getConfig()->get('memcached')->port;
        $this->compress = isset($params[2]) ? $params[2] : getConfig()->get('memcached')->compress;
        $this->expiry = isset($params[3]) ? $params[3] : getConfig()->get('memcached')->expiry;
    }