Content-Rewriter, Proxy, Broken Images, and makeRequest

[Taylor Singletary <ta...@gmail.com>]

Hi all,

I've had some trouble getting this element of ShinDig to work in the several
months I've been wrangling with the Java ShinDig implementation.

Here's the problem:

When an outbound GET makeRequest is receiving an HTML payload, ShinDig's
content rewriter replaces src tags like images with an URL to the OpenSocial
proxy.

The bad side: all images on the page are then broken when rendered inline
with the HTML surrounding it.

The good side: if I manually browse to the URL with the proxy indicated, I
can see the image.

Looking into this deeper, it seems the reason the images will not display
inline in the HTML is because the Content-Length (and maybe the Content-Type
though I think that's coming through correctly) gets munged with the Proxy,
causing the browser to refuse to display the image inline.

Has anyone else run into this and have any solutions to propose?

Thanks,
Taylor

Re: Content-Rewriter, Proxy, Broken Images, and makeRequest

[John Hjelmstad <fa...@google.com>]

Can you give a minimal example of the raw input to makeRequest and the
faulty output? Ideally something I could replicate locally..
--John

On Thu, Oct 9, 2008 at 4:51 PM, Taylor Singletary <
taylorsingletary@gmail.com> wrote:

> Hi all,
>
> I've had some trouble getting this element of ShinDig to work in the
> several
> months I've been wrangling with the Java ShinDig implementation.
>
> Here's the problem:
>
> When an outbound GET makeRequest is receiving an HTML payload, ShinDig's
> content rewriter replaces src tags like images with an URL to the
> OpenSocial
> proxy.
>
> The bad side: all images on the page are then broken when rendered inline
> with the HTML surrounding it.
>
> The good side: if I manually browse to the URL with the proxy indicated, I
> can see the image.
>
> Looking into this deeper, it seems the reason the images will not display
> inline in the HTML is because the Content-Length (and maybe the
> Content-Type
> though I think that's coming through correctly) gets munged with the Proxy,
> causing the browser to refuse to display the image inline.
>
> Has anyone else run into this and have any solutions to propose?
>
> Thanks,
> Taylor
>