Hi Alex, Thank you for mentioning this. It sounds like this is a bug, so I'm digging into this now. I think the correct behavior would be that if the library is loaded over HTTPS then the image URL that we attempt to fetch should be HTTPS as well. For now you can work around this by pulling in the script directly. The URLs of the libraries are documented on
http://code.google.com/apis/ajaxlibs/documentation/index.html#jquery and http://code.google.com/apis/ajaxlibs/documentation/index.html#swfobject And you can load these over HTTPS instead at the URLs provided in the "path" section of the documentation. Here are some examples: https://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js https://ajax.googleapis.com/ajax/libs/swfobject/2.2/swfobject.js Happy coding, Jeff On Oct 8, 9:47 am, kingofthelowend <[email protected]> wrote: > Jeff, > > Good explanation. Unfortunately, this is breaking our SSL pages > because even though the jQuery and SWFObject libraries are loading via > HTTPS, the 1x1 stats .gif is loading via HTTP. For now we can revert > to linking directly to the secure scripts, but this is an issue. > Also, it seems to only happen in the transition to a secure area from > an unsecure area. > > Thanks, > Alex > > On Sep 10, 6:22 pm, "Jeff S (Google)" <[email protected]> wrote: > > > Hi Paul, > > > Good question! Because many loads of the libraries are cached, we > > never see requests for them. In order to better estimate our traffic, > > we use this request to inform us what has been loaded. Also, the > > request happens asynchronously much after the page loads so that we > > don’t slow down the application performance. These signals are used by > > us for capacity planning purposes. We have expanded some of our > > operations and grown our capacity. The signals we get from these logs > > are directly responsible for our ability to meet the needs of the > > community and help ensure global, low latency access to the system. > > For example, when a new library is released, we tend to see a traffic > > spike as we serve new and not yet cached versions of these libraries. > > Without information on how often these libraries are being requested > > from us, we have a more difficult time anticipating how large this > > spike might be. > > > If you don’t want these requests to happen, you can include the > > libraries directly instead of through the loader. The direct links > > are all listed > > here:http://code.google.com/apis/ajaxlibs/documentation/#AjaxLibraries > > > Happy coding, > > > Jeff > > > On Sep 7, 3:33 am, Paul Thomas <[email protected]> wrote: > > > > Hi > > > > I'm currently trying out the google hosted versions of jQuery. It's > > > great to be able to use the libraries from google's servers, so > > > thanks. > > > > I have noticed when I've been debugging my AJAX however that extra > > > calls appear to be being made to google's servers after the library > > > has already been downloaded. These URLs look like the following: > > > >http://www.google.com/uds/stats?r0=el%7Cjquery&nc=1252319019940_15016 > > > > They come from an image that is being embedded into the DOM, > > > presumably by some google javascript. > > > > What is the purpose of these extra calls? Is google monitoring sites > > > that use the hosted APIs? If so what data is being collected and what > > > is it being used for? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google AJAX APIs" 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-ajax-search-api?hl=en -~----------~----~----~----~------~----~------~--~---
