OC 6 doesn't support spdy

[cyberdaemon]

Expected behaviour

Support for spdy

See more informations: https://code.google.com/p/mod-spdy/

Actual behaviour

Owncloud is not accessible anymore

Steps to reproduce

1. install spdy
2. try to access owncloud
3. take a look at the nice error :)

Server configuration

Operating system: Centos 6.5

Web server: Apache 2.2.15

Database: MySQL 5

PHP version: 5.3

ownCloud version: 6 stable

Client configuration

Browser: FF

Operating system: Linux

Logs

Web server error log

sorry, none

ownCloud log (data/owncloud.log)

sorry none

[bantu]

@cyberdaemon What exactly is the text of the "nice error" you are referring to?

[tribut]

I am running mod_spdy and don't encounter any errors except for the documents module not loading (see my bug against documents owncloud-archive/documents#166). When mod_spdy is disabled, documents load as expected.

(Debian wheezy, Apache 2.2.22-13+deb7u1, php 5.4.4-14+deb7u7 using mod_fcgid, spdy 0.9.4.1-r397)

[arnowelzel]

Same for me - with SPDY everything works fine (including sync via cardDAV/calDAV) except the documents module as in described in owncloud-archive/documents#166.

If ownCloud does not work at all with SPDY the problem may be using PHP as Apache module and not via CGI or FCGI - but this is a known limitation, see https://developers.google.com/speed/spdy/mod_spdy/:

In particular, if you'd like to serve PHP over mod_spdy, it is highly recommended that you use mod_fcgid rather than mod_php, as some PHP libraries are not thread-safe; using mod_fcgid will run PHP in a separate process, thus avoiding the thread safety issues.

Concerning the documents module problem: SPDY handles many requests in parallel streams and therefore a JavaScript relying on the sequential execution of the requests may fail (e.g. one Ajax call is made and then a second one and it is expected that the first Ajax call will also return results first and not after the second call etc.) - but this is just a wild guess.

[cyberdaemon]

*** glibc detected *** /usr/sbin/httpd: double free or corruption (out): 0x00007fd8a8000a50 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x76166)[0x7fd8bb343166]
/usr/lib64/libxml2.so.2(xmlResetError+0x22)[0x7fd8b10d6302]
/etc/httpd/modules/libphp5.so(+0xccba4)[0x7fd8b1b48ba4]
/etc/httpd/modules/libphp5.so(+0x21cc2c)[0x7fd8b1c98c2c]
/etc/httpd/modules/libphp5.so(zend_hash_reverse_apply+0x44)[0x7fd8b1ca3424]
/etc/httpd/modules/libphp5.so(+0x21b69d)[0x7fd8b1c9769d]
/etc/httpd/modules/libphp5.so(php_request_shutdown+0x395)[0x7fd8b1c454e5]
/etc/httpd/modules/libphp5.so(+0x2a3d67)[0x7fd8b1d1fd67]
/usr/sbin/httpd(ap_run_handler+0x70)[0x7fd8bcdbdbb0]
/usr/sbin/httpd(ap_invoke_handler+0xce)[0x7fd8bcdc146e]
/usr/sbin/httpd(ap_process_request+0x1c0)[0x7fd8bcdccb30]
/usr/sbin/httpd(+0x379a8)[0x7fd8bcdc99a8]
/usr/sbin/httpd(ap_run_process_connection+0x68)[0x7fd8bcdc56b8]
/usr/lib64/httpd/modules/mod_spdy.so(+0x16d5f)[0x7fd8af69ed5f]
/usr/lib64/httpd/modules/mod_spdy.so(+0x10419)[0x7fd8af698419]
/usr/lib64/httpd/modules/mod_spdy.so(+0x3c54d)[0x7fd8af6c454d]
/usr/lib64/httpd/modules/mod_spdy.so(+0x3c54d)[0x7fd8af6c454d]
/usr/lib64/httpd/modules/mod_spdy.so(+0x38a7b)[0x7fd8af6c0a7b]
/usr/lib64/httpd/modules/mod_spdy.so(+0x1be31)[0x7fd8af6a3e31]
/lib64/libpthread.so.0(+0x79d1)[0x7fd8bb6689d1]
/lib64/libc.so.6(clone+0x6d)[0x7fd8bb3b5b6d]

[arnowelzel]

@cyberdaemon This is not a specific problem of ownCloud - ownCloud just triggers the problems in your server setup which exist anyway.

You use PHP as a module - which is not recommended due to thread safety issues of PHP. Change this to CGI or FCGI and it should generally be OK (except the document module - but this is another story).

Also see https://developers.google.com/speed/spdy/mod_spdy/ which I already mentioned.

[bantu]

@arnowelzel Thanks

Closing as such.