SSL Enforcer and MyeBay

[ken-bke-syocfo9k5w]

I am gettting an error whenever I try and access my.eBay.com which indicates to me it is not secured. 

 Non-secure HTTP Connection Blocked by SSL Enforcer

Requested URL: http://my.ebay.com/ws/eBayISAPI.dll?MyeBay

✗

Secure alternative: https://my.ebay.com/ws/eBayISAPI.dll?MyeBay HTTPS is not available for https://my.ebay.com Secure alternative: https://my.ebay.com/ws/eBayISAPI.dll?MyeBay HTTPS is not available for https://my.ebay.com my.ebay.com - checking HTTPS availability Check result found in cache Connection to 66.135.212.212:443 established SSL handshake succeeded Check SSL certificate succeeded Dead loop detected in HTTP response

01/02/18 19:54:41 
SSL Enforcer v1.31

[dollybeauty]

There is no domain my.ebay.com. Firefox redirects to https://www.ebay.com/

[berserkerplanet]

>>There is no domain my.ebay.com. Firefox redirects to https://www.ebay.com/

Whaaaattttt?????

my.ebay.com is still a perfectly valid ebay subdomain and I use it for half of my eBay activity. It works as either HTTP or HTTPS in FIrefox (3.6.24 and 31 - don't know/don't care about FF50 something versions)

http://my.ebay.com/ws/eBayISAPI.dll?MyEbayBeta&CurrentPage=MyeBayNextSelling
http://my.ebay.com/ws/eBayISAPI.dll?MyEbayBeta&CurrentPage=MyeBayNextSold
etc.

No idea about OP's issue with SSL enforcer since https://my.ebay.com is secure and works for me.

Wonder if it's a TLS issue - my older browsers use TLS 1.0. 1.1, and 1.2, but newest browsers have jumped the gun on TLS 1.3 which isn't ready for primetime and isn't widely adopted (ie: SSL enforcer is assuming something or doing something that involves TLS1.3 which I'm not sure eBay supports well - total guesswork and outside of my pay grade)

[dollybeauty]

Oops. With all of the https, active content and redirections, I made a mistake. My bad.

[berserkerplanet]

I thought I made a mistake once too, but turns out I was mistaken. If nothing else, now I know for sure you are human

[berserkerplanet]

Actually does appear to be a bug with eBay redirection when visiting the subdomain root via https://my.ebay.com/ directly.

It results in a dead end redirection to http://my.ebay.com:443/ws/eBayISAPI.dll?MyeBay which is an empty document.

That may be why SSL Enforcer is complaining.

An SSL Enforcer redirect of insecure http://my.ebay.com/  to secure https://my.ebay.com/ results in a subsequent eBay redirect back to insecure http://my.ebay.com:443/ws/eBayISAPI.dll?MyeBay which is a dead end.

(I didn't check to see what security certs,etc were flying back and forth on that last redirect - may be that there is no actual SSL support on port 443 for that URL which might explain the dead end condition)

Simple solution is for OP to not try to go to http://my.ebay.com/ through SSL Enforcer (whitelisting?) or to use https://my.ebay.com/ws/eBayISAPI.dll?MyeBay or http://my.ebay.com/ws/eBayISAPI.dll?MyeBay which are fine.