On Wed, 24 Feb 2010 10:51:08 +0100 Johannes Ahlers <[email protected]> wrote:
> Hello, > > the problem occurs when our pootle-page is accessed via https. > Internal we access the server via http. This works fine. Our > translators access an apache proxy via hhtps which forwards the > request to the internal pootle server. It seems the java-scripts > (jquery) are delivered via http instead of https and so it doesn't > work on client side (when I use FireFox or Opera). But if I open the > external page with Internet Explorer I got the message "some contents > are insecure" but here the java-scripts seems to work. The > edit-fields have the correct height. I searched FireFox's security > options, but I can't find any option, to make it trust our external > page and load the scripts in a way that it works. we don't specify protocol at all while linking to javascript files (check html source code). so I can't see why the javascript would be served from http and not https. it might be that page caching is introducing problems, is this problem happening to logged in users (only anonymous requests are cached). cheers, Alaa ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
