SSL AJAX call failures on custom domains

Brian Barnes <[email protected]>
Newsgroups gmane.comp.web.blogger.api
Message-ID <[email protected]>
Hi, I posted this on another list and was directed here, as this is where 
the scripting code is discussed.

My blog is at www.paradeofhorrorables.com.  This is a custom domain, 
redirected to blogger.  There are problems with the design scripts when you 
do this.

Basically, when you have a custom domain, the "do not track your own page 
views fails."  The problem is that the site attempts an AJAX call back to 
google's servers through the custom domain, but the AJAX call is HTTPS, 
which fails because custom domains reject SSL calls.  From anywhere, for 
example:

Hitting https://www.paradeofhorrorables.com fails, but 
http://www.paradeofhorrables.com does not.

Obviously, there's no certificate, self-signed or otherwise, and supposedly 
blogger doesn't support that, anyway.  So, I propose a fix, just try-catch 
the AJAX call and if it fails, try again without the SSL, i.e.:

try {

// the https ajax call to set the no track cookie

}

catch (e) {

// an http ajax call

}

// do something with return

I've seen this question asked a lot of your forums, and there's never a 
solution.  Here's the cause, and hopefully a solution you guys could work 
with.  I might be off base as I don't have full knowledge of your code and 
servers, but I suspect this would work.  Regardless, thanks for the time, 
and any further questions or testing I'd be happy to help.

[>] Brian

-- 
You received this message because you are subscribed to the Google Groups "Blogger Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/bloggerdev.
For more options, visit https://groups.google.com/d/optout.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.