Hi,
Had some questions about server host and port in container.js - in
particular the values that are used in Uri generation (ex:
gadgets.uri.proxy.host - set from defaultShindigProxyConcatAuthority
in container.js). Currently this value either comes from web.xml, or
a system property (jetty
We ran into the same issues here and we had to write an extension to inherit
the values from the request.
+1 to add this as configurable behavior
- Mike
--
Liferay West Coast Symposium
September 8-9, 2010
Anaheim, CA
www.liferay.com/wcs
--
Follow us on Twitter: liferay
On Sep 15, 2010, at 7:26
It might be tough to change the assumption that shindig host and port are
not static and could change at runtime with the http request.
It might be easier to just add a rewriter that moves the proxied resources
from shindig authority to the host/port you want (which is the host port of
the HttpRequ
Thanks for the feedback. It makes sense to look at adding a rewriter
to do this. Will be looking at this in the next few days.
Mike - if you don't mind sharing, how did your extension work?
Mark
On Wed, Sep 15, 2010 at 10:48 PM, Gagandeep singh wrote:
> It might be tough to change the assumpt
Hi Mark,
Of course. Our code is open source. You can download it here:
http://sourceforge.net/projects/lportal/files/Liferay%20Plugins/6.0.5/opensocial-portlet-6.0.5.1.war/download
The src is in the WEB-INF folder. Look for ShindigFilter and
LiferayJsonContainerConfig.
Hope that helps.
- Mik
