asked by Technext

You have a few problems, the cause of them is not entirely clear.

One thing to bear in mind is this: when you're using Apache HTTPD in front of Tomcat, if you can get it working under normal HTTP then configuring HTTPS should be simple.

HTTP and HTTPS in Apache HTTPD are treated as separate VirtualHosts, so it should just be a case of ensuring that whatever configuration you've applied to the HTTP virtual host is also applied to the HTTPS host.

This can be achieved with ease, by placing all of the mod_jk or mod_proxy (in your case) configuration in an external file and using the 'include' mechanism.

The HTTP address you provide is using the port 8080, which Tomcat specifies as the default port for it's own HTTP connector - suggesting that you're not connecting via Apache HTTPD when you make that request.

The ProxyPass statements point both /abc and / to the same path, which is a subpath of the application /abc - this seems unusual.  I'd expect to see the path http://server:8080/abc, without the '/implement' extension, this may be the source of some of the missing images.

The last issue, regarding the message "line 56 Object expected" is likely to be a Javascript problem, possibly caused by a script file experiencing the same 404 as the images.

In order to debug the problem, it would be better to start with a fresh configuration - discard whatever you have so far, or copy it to a backup.

The Fiddler or ieHttpHeader plugins for Internet Explorer will make it easier to examine which resources are, or are not being served correctly.

You will need to examine both the Apache HTTPD and Tomcat access logs to see which server is serving each request and check that the result is the expected one.

Configure the HTTP instance and test it thoroughly before attempting the HTTPS configuration.

answered by pidster on June 16, 2011 11:39 AM

Read More