Web devs beware: the just-released Chrome 21 now blocks mixed content. If you're serving a https page that loads anything over http, that insecure load is now blocked silently (a warning message appears in the console but the user sees nothing).
I'm pretty sure this change was the culprit.
And I'm not seeing a setting that can modify this behavior either.
Wasted a couple hours today trying to figure out why all our pages were broken. Yes, yes, it would be nice if we could serve everything over https, but there are a few resources we rely on that we just can't.
Update: this only happens for javascript files, not images.
Thursday, August 02, 2012
Tuesday, January 17, 2012
Confluence on OS X
Wasted the morning figuring out how to install Confluence on OS X and getting it to work as a daemon. In case I ever need it again:
- How to start/stop Confluence as a daemon. Not sure why it's not in the 4.x documentation.
- Exposing Confluence on port 80 - here's the short version in case it disappears:
- Create the following configuration file for Apache2 in
/private/etc/apache2/other:
<Proxy *> Order deny,allow Allow from all </Proxy> ProxyRequests Off ProxyPreserveHost On ProxyPass / http://localhost:8090/ ProxyPassReverse / http://localhost:8090/
- Start (or restart) Apache. Go to System Preferences -> Sharing. Tick “Web Sharing”. Without the file above, all you'll see on http://localhost is a page saying "It works!"
- Create the following configuration file for Apache2 in
This is working with Confluence 4.1.3 and on OS X 10.7.2.
I shudder to think of the amount of hair pulling I'd have went through if I'd tried to get this set up without Google (or equivalent).
Subscribe to:
Posts (Atom)