Hi,

Looks like proxy rewriting of images is failing with the new
DefaultProxyUriManager class.

Specifically rewriters are not setting the container value, which causes the
request to be rejected.  The default code that uses values from
java/config/shindig.properties and the javascript code for getProxyUrl do
not set container values, thus proxying is all broken for these use cases.

It appears that ContentRewriterUris tries to use the container specific
value of gadgets.rewriteProxyBase, failing that it uses the injected value
of shindig.content-rewrite.proxy-url which maps to /gadgets/proxy?url=

I'm a bit concerned that there are other issues like this lurking about...

Is it possible that we can come up with a common idiom that handles all of
these situations?  Perhaps a parameterized Uri concept that could be applied
here.

Reply via email to