Hi Nati,

I'm guessing it's a permissions problem. When I try to load your JPEG
directly in my browser, I get an HTTP 403 (Forbidden: You don't have
permission to access /kids.jpg on this server). My guess is that when
IE tries to load the image in the context of iGoogle, it runs into the
same trouble - possibly because of the referer? But once your browser
has the image in cache, it's happy to show it, whatever the context.

So I'd recommend looking at whatever protections you have on images on
that server. Perhaps a mod_rewrite rule to prevent other sites
hotlinking to your imagery?

String

On Dec 6, 1:46 pm, Nati <[EMAIL PROTECTED]> wrote:
> Hi,
> I've created a simple xml file, includes "<Attribute
> name="header.center_image.url">http://natis55.blackapplehost.com/
> kids.jpg</Attribute>". While testing the xml file (writing 
> "http://www.google.com/ig?skin=http://natis55.blackapplehost.com/kids.xml"; as
> an address), the picture I supplied doesn't appear, though the picture
> itself is hosted on the same host server as the xml file is.
>
> But, when I type in the address bar the address of the hosted picture
> ("http://natis55.blackapplehost.com/kids.jpg";), I do see the picture,
> and from that moment, while I type again "http://www.google.com/ig?
> skin=http://natis55.blackapplehost.com/kids.xml"; I do see the picture,
> even I logout and log in, until I close Internet Explorer.
> Once I close the IE, I first need to type address of the pictue
> itself.
> The xml is not meant to be published, It's just for my private use.
> How do I get rid of typing the address of the picture first?
> 10x, Nati.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Themes API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-themes-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to