Gmail feeds - HTTP or HTTPS

[Jkon]

Just a quick question. I have always used Url=http://#username#:#password#@gmail.google.com/gmail/feed/atom in my Gmail skins.
Today, I had a user who could not obtain his feed using this and it turns out by adding an "s" to "http" solved his problem.A quick wiki session informs me that the added "s" dedicates the SSL protocol to http.So, should I have been using https all along. As both http and https seem to work for me and not for him,could adding the "s" to my code in future present problems for others.

[jsmorley]

Won't be any problem with a site that supports https (SSL), but might be if it doesn't, so you don't want to just assume that any feed is going to support secure sockets or transport layer security.

[Jkon]

support secure sockets or transport layer security

That nearly clattered me as it flew over my head. Way too technical for me.My intention would only be to add it to my gmail feeds,as I presume if the feed supports it then it's best to use it,but if gmails feed supports it in one location, does it necessarily
support it everywhere.

[jsmorley]

That nearly clattered me as it flew over my head. Way too technical for me.My intention would only be to add it to my gmail feeds,as I presume if the feed supports it then it's best to use it,but if gmails feed supports it in one location, does it necessarily
support it everywhere.

I'm pretty sure it does.

[Jkon]

Cheers.I'll try adding it in future.I doubt it can cause me any more problems then it not being there.Either way,at least today, I learned what could be the cause of some peoples problems.Was a solution ever found for German gmail accounts.I thought I say someone post something about it in the last few months but couldn't find the post again.Thanks again.

[Kaelri]

Gmail defaults to HTTPS for all connections. You should have your skins use a secure connection whenever it's available - there's really no downside.

[Jkon]

Well,that clears that issue up nicely.thanks for that Kaelri.