"BUG?": Checkout

I am unable to proceed from my shopping basket, and after a little investigation I've narrowed down the problem.

My web filter is blocking the site because of the keywords "gay" and "thong". This makes no sense to me whatsoever, why would these words be in anyway associated with the checkout page's "proceed" button? Im tring to purchase bible software here I fail to see where my filter has found these words, but in any case, perhaps someone who can would like to investigate that.

Find more posts tagged with

Comments

Cameron Watters (Faithlife)

We're looking into it. It turns out that each sequence of characters you mention does occur on the checkout page. They are a part of automatically generated hashes:



vtG8WCYM-UUQu6Hvwsp3T7NKerNZ74EFH4Ld5hA583TwoEuk4JH05HhWE7j0xGjg00mtsCZaOE-QgBaBZEM2enY20BR2x8yP686spqoKQP_hGJbdEPekd3KI-JsYiMgAypHgpKATiN6D4KrkC86P1prEKPVZjWYHK2WvquFwBbWyaPKh0

xCxOKcfTSw33AqaSh44ldMagYjBA7lL9BiB107GahbM9eKCV_MHpkxlsBAZ_THoNGEgQkJkcm8Jr_iqCYUiXFKDZZV81

Their occurrence in these strings is, of course, completely coincidental. We'll see what can be done to prevent it.

David Ladiges

The simplest solution here would be adding *.logos.com to your filter's whitelist or ensuring that your keywords are preceded or followed by a whitespace character before they match your filter. Either of those workarounds would prevent the filter hits you are seeing.

I don't think we going to be able to focus too much on preventing
automatically generated hash values and encrypted fields from containing random strings of
characters. The ViewState field contents would be especially hard to
filter in any way that is performant. The first solution on our end that comes to mind would be buffering the entire page output so we can check the ViewState and if it matches any words in a particular word list then altering the contents of the ViewState and regenerating the page and repeating the entire process again to make sure that the new ViewState contents don't match the filter. Not exactly an efficient process.

Fortunately, we are moving away from using ViewState wherever possible as we move to newer technologies so eventually this problem may go away, but it's going to be a long while before we are able remove it entirely.

Sam Warner

https://community.logos.com/discussion/comment/287549#Comment_287549

I made my order on a different computer to get around it, but I thought it worth pointing out as im sure im not the only person running filter software who'll run into this.