Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Jei jums reikia pagalbos, užduokite naują klausimą.

when logging in to https://commercial.searspartsdirect.com/partsdirect/commercialLogin.pd I get redirected to https://sso.shld.net/shccas/shcLogin which is the

hidemand
hidemand
more options

this does not happen with google chrome on the same computer nor does it happen with firefox on my other computer (win vista) nor does it happen on my iphone. i have cleared history, cookies, etc. to no avail. I am submitting this using google chrome because submitting it from firefox gives an error loading page when submitting. so now there's a new symptom?

this does not happen with google chrome on the same computer nor does it happen with firefox on my other computer (win vista) nor does it happen on my iphone. i have cleared history, cookies, etc. to no avail. I am submitting this using google chrome because submitting it from firefox gives an error loading page when submitting. so now there's a new symptom?

All Replies (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

That appears to be a legitimate Sears website. The redirects have been mentioned in various discussions (found in Google) for several years.

If the problem is that Firefox is pausing and asking you to approve the redirect, you can bypass that this way:

orange Firefox button or Tools menu > Options > Advanced

On the General mini-tab uncheck Warn me when web sites try to redirect or reload the page

Regarding an error on these forums, that doesn't sound related, and if it occurs multiple times (i.e., not just a one-time server hiccup) then we should work on that separately.