String, Thanks for the reply. I realize iGoogle reads the gadget definition themselves and serves it to the user. My attempted use of https in this case wasn't for secure delivery per se, but for convenience, as the rest of my application is based on https.
In my humble opinion this is just another touch point / opportunity for iGoogle to break my gadgets. For example, there appears to be an (undocumented, surprise, surprise) upper limit on the size of the gadget definition. Also, this antiquated design breaks support for external javascript, relative URLs, etc. (again unless using type=url). External javascript referenced in a gadget definition, for example, won't work in Google Chrome or Safari. For the above reasons, and many more, my advice for anyone with the unfortunate task of developing for igoogle: Use type="url" exclusively, making your google gadget a simple wrapper of html content served and controlled by you, each and every time a user fires up a gadget. And I think the non-answer from anyone at google on this forum topic and on my feedback to the gadget checker confirms my suspicions that iGoogle is a poorly documented, virtually unsupported, and developer- unfriendly platform. This is too bad, as feature-wise, it is very complete, and I especially appreciate their recent work expanding it to the mobile space. I think its another example of the mentality at Google that has historically lead to incomplete products in perpetual Beta release. -Jonathan On Jul 7, 11:59 pm, String <[email protected]> wrote: > On Jul 1, 8:55 pm, jonathaz <[email protected]> wrote: > > > If HTTPS is not allowed for serving gadget definitions, it would be > > very much appreciated if this were documented, reported as such in a > > more specific error message, and also if the Gadget Checker would > > report it as an error. > > Jonathan, > > I would point out that gadget definitions aren't served to the user's > iGoogle page from the URL you host them at. Google loads the > definition and uses it internally to generate an iframe, which is then > what gets served to the user. So even if you got an HTTPS definition > URL to work, that's no help in getting your gadget delivered securely. > The iframe is still served over HTTP from Google, even if the user has > requested their iGoogle page securely (as in HTTPS://www.google.com/ig). > > IOW, if you're interested in secure content delivery, gadgets aren't a > good fit. You might be able to serve HTTPS via a type="url" gadget, I > haven't tried. > > String --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" 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-Gadgets-API?hl=en -~----------~----~----~----~------~----~------~--~---
