Hi Daniel, I don't think I can help with your problem, but I am wondering 2 things when looking at your configuration:
1. You use mod_proxy / mod_proxy_html --> why? We use mod_jk and Tomcat's AJP Connector. So far we have no problems with this setup at all. Is there some advantage you see to using mod_proxy over mod_jk? I haven't been able to answer this question for myself, and would be interested in knowing the rationale behind the choice of mod_proxy. 2. Why are you rewriting URLs in the content? IMHO rewriting content is a recipe for trouble! You could simply install magnoliaPublic in the ROOT context (rename the webapp folder from "magnoliaPublic" to "ROOT" and rename the folder "WEB-INF/config/magnoliaPublic" to " WEB-INF/config/ROOT"). If your public instance were running in the ROOT context you would not need to use mod_proxy_html at all, and it would improve performance, since Apache would no longer have to inflate-rewrite-compress each request... Is there a good reason for leaving magnoliaPublic and using mod_proxy_html? Sorry that I only have stupid questions and can't really help with your actual problem... Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Daniel (via Magnolia Forums) Gesendet: Mittwoch, 23. Mai 2012 15:18 An: Magnolia User List Betreff: [magnolia-user] Magnolia 4.5.1/4.5.2 behind Apache2 with mod_proxy_html -> IE lt 9 css-problem Hi magnolia-users, since update our cms from 4.4.6 -> 4.5.x, we have a problem with IE lt 9 and css. The Config: Server: Ubuntu 10.04 LTS, Apache 2.2.14 CMS: Magnolia CE 4.5.2, standard-templating-kit 2.0.2 (with only "pimped css", js etc. are untouched) Everything works fine, but on the production-system behind the apache proxy, IEs lt 9 has problems with css (or more ...?). xx.conf has following parameters [code]<VirtualHost www.xx.eu:80> ServerName www.xx.eu RewriteEngine On RewriteRule ^/$ /xx.html [P] ProxyPass /docroot/ http://localhost:8081/magnoliaPublic/docroot/ ProxyPass /dms/ http://localhost:8081/magnoliaPublic/dms/ ProxyPass / http://localhost:8081/magnoliaPublic/ ProxyPassReverse /docroot/ http://localhost:8081/magnoliaPublic/docroot/ ProxyPassReverse /dms/ http://localhost:8081/magnoliaPublic/dms/ ProxyPassReverse / http://localhost:8081/magnoliaPublic/ ProxyHTMLExtended On ProxyHTMLMeta On ProxyHTMLStripComments Off ProxyHTMLURLMap /magnoliaPublic/docroot/ /docroot/ ProxyHTMLURLMap /magnoliaPublic/dms/ /dms/ ProxyHTMLURLMap /magnoliaPublic/ / ProxyHTMLDoctype XHTML Legacy SetOutputFilter INFLATE;proxy-html;DEFLATE BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4.0[678] no-gzip BrowserMatch "MSIE 6" no-gzip BrowserMatch "MSIE 7" !no-gzip !gzip-only-text/html BrowserMatch "MSIE 8" !no-gzip !gzip-only-text/html SetEnvIfNoCase Request_URI .(?:gif|jpe?g|png|pdf)$ no-gzip dont-vary ExpiresActive on ExpiresDefault "access plus 1 day" </VirtualHost>[/code] If ProxyHTMLExtended is Off, css is processed but no images (from dms) are loaded. So, i think the problem is primary in a magnolia js, secondary in apache mod_proxy_html. I hope someone can resolve the problem or give a little support ;-) Have a nice day Thanks and greetings DS -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=9f1e95ac-b2e7-4d24-b6c0-240a6defede1 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
