[RESOLVED NOT NS]Search box not functioning while using ssl?

[scream258]

I have been developing an ecommerce site and I noticed a small problem. I love NoScript and refuse to surf without it, but this problem bugs me, as it may affect some of my customers. I'm hoping someone here can explain to me what is causing the problem and provide a solution, if possible. I'm not sure if this is a problem on my end, or if it affects others also.

Go to http:xx.screambodyjewelry.com -- allow it, and then try to click in the search box at the top. It works fine and you are given search results once you hit go.

Now enter SSL mode.

Go to https:xx.screambodyjewelry.com -- allow it if needed, and try to click the search box. I am unable to click on it! The box doesn't even behave like a text box, but like I said, only while SSL is being used.

Any idea what is causing this? Is there a way to alter the site code to fix this issue?

It really isn't a big deal as it will probably only affect a small number of our users, but I am curious about a cause/solution.

Keep up the great work, NoScript rocks!

Many Thanks!

[scream258]

After a little more investigation I seem to have come to the wrong conclusion...

I guess it has nothing to do with SSL, but whether or not I am logged into the site.

When I'm logged out of the site the search box works fine.

When I log in (which starts SSL) the search box stops functioning.

I am able to use the search box while logged in if I am using IE. But not in Firefox w/ NoScript.

Any ideas?

[GµårÐïåñ]

glad you figured it out. Thank you for letting us know. If there is anything Giorgio or anyone else can suggest, I am sure they will let you know.

[scream258]

I found out that the issue wasn't what I originally thought, but an issue still exists.

The search box works fine while not logged in. Once logged in it stops functioning.

Disabling NoScript resolves the issue and I can use the search box whether I am logged in or not.

No ideas?

[GµårÐïåñ]

I know and that's why I thanked you for letting us know its not THAT problem and if someone has something to add they will, otherwise the thread would have been marked RESOLVED, it wasn't so the issue is still open. I don't have an idea because my assumption is simply that the developer is using their code to search on http and so when https it will obviously be an issue, especially if you have Tools|Options|Advanced|HTTPS|Cookies|Enable Automatic Secure Cookies Management checked. Otherwise, I don't know, so once again I will leave it up to the others who might.

[Tom T.]

I tried to create a test account, as I have done on other similar issues. However, since this is a wholesale-only site, it wouldn't let me create an account without full billing and shipping information, (address, phone #, etc.) and other info that I don't care to give.

Could you create a test account and PM the login credentials to me, so that I can see if I can reproduce your issue? I promise I won't buy anything. (nor disclose the credentials, which you can delete as soon as the issue is solved).
I'm not into body jewelry anyway, no offense.

[scream258]

Thanks for looking into this, Tom. I've PM'd you login credentials.

[GµårÐïåñ]

@scream, since I see that you signed up for an account, I went ahead and combined your previous anonymous posts to your account so that you can find the posts easier as well as get credit for them. Let me know if there are any in other threads and I will update them as well. You can PM me the links. Tom will get back to you as soon as he has tested the issue, good luck and hopefully one you will update the thread for the benefit of others. Thank you.

[Tom T.]

Investigating....

[Tom T.]

I have a quick work-around for you: Leave the search box empty and click "Go". You'll be taken to a page that has another search box in the middle, which works fine.

Continuing to investigate why the main one doesn't work.

[Tom T.]

FWIW, I'm getting the identical results in IE6, with the site in the Trusted zone and all security settings set either to "Enable" or to "Prompt", i. e., allowed.

[GµårÐïåñ]

My suspicion is as stated before that its a codebase issue that is not properly honoring protocol within its internal logic. Your results suggest now strongly that it is the case. Will look forward to anything else you find. Thank you.

[Tom T.]

Confirming Guardian. I disabled NoScript completely, and still reproduced the issue as described. So this is not a NoScript issue.

Ordinarily, the next recommendation would be to do a Standard Diagnostic to check for extension conflicts, corrupt extension files, etc.; however, the fact that the issue is reproducible in IE with full permissions given suggests that the site is coded improperly.

Am marking Resolved, as not being a NoScript issue but a site-design issue.

I'll delete the credentials from my PMs. Thanks.

[scream258]

Thanks for investigating. Very odd indeed. Using IE8 I am unable to replicate the issue (as of right now). But, this seems to be a fairly random failure, which is what lead me to believe it was NoScript. At one point the search box stopped working, I disabled the add-on and it began working. I just went back and tried again with the add-on disabled, and what do you know -- not working.

I've brought the issue up with the Aspdotnetstorefront but chances are they will do nothing to follow up on it. Generally forum posts that note bugs in their software are just deleted. They've become notorious for this.

Again, thanks for investigating. I will let you know if they have anything to say about it.

[Tom T.]

But, this seems to be a fairly random failure, which is what lead me to believe it was NoScript.

Probably not. If NoScript is causing a problem, it usually tends to do so consistently, if the same circumstances are reproduced. It's possible, but not the majority of cases. You were "unlucky" to have it work with NS disabled. I got the same failure immediately with NS disabled, which is a quick answer.

I've brought the issue up with the Aspdotnetstorefront but chances are they will do nothing to follow up on it. Generally forum posts that note bugs in their software are just deleted. They've become notorious for this.

What's the point of the forum, then? And why would anyone buy their product? And how will it ever improve? And ...

We try to fix validated bugs ASAP here -- often, the same day. Sometimes, a few hours.

Again, thanks for investigating. I will let you know if they have anything to say about it.

No problem -- happy to do it. And yes, it would be interesting to see what they say. Never know when someone else might post the same issue.

Cheers.