Joachim Seibert wrote:
But in this case I can't find any reason, why an absolute link would
be important here.
It's possible to configure status.net so that theme files are located on
a different physical or virtual server. This can speed up page rendering
significantly, and use CDNs or just fast static-file servers (we use
lighttpd for the StatusNet Cloud) to make thing load faster.
So: we need absolute URLs to make that work.
However! There's code in the current testing branch of StatusNet that
will become StatusNet 0.9.0 that will optionally and flexibly generate
HTTPS links for all content files (avatars, theme, attachments,
JavaScript, and backgrounds).
The only thing I've had problems with in testing has been the Creative
Commons image, which apparently isn't available under HTTPS. Best idea
for a work-around is to copy it to a local dir and serve it over HTTPS
from there. (I think a lot of folks who want all-HTTPS would be setting
their license type to 'confidential' or 'allrightsreserved' anyways.)
-Evan
--
Evan Prodromou
CEO, StatusNet, Inc.
e...@status.net - http://identi.ca/evan - +1-514-554-3826
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev
