Closed Bug 310836 Opened 19 years ago Closed 19 years ago

duvalclerk.com - Government site sniffs all non-WinIE UA strings b/c site uses VBScript

Categories

(Tech Evangelism Graveyard :: English US, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: p00ldy, Unassigned)

References

()

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4

This extends to any browser on any platform that does not send an IE6 UA string.
 When this doesn't happen, you receive this:

"Attention Firefox/Netscape/Linux/MacOS Users:

This site is designed for use with Microsoft Internet Explorer 6.0. You may need
to switch to view this site properly, or make adjustments to your browers's
default security configuration. VBScript and JavaScript are required for the
proper function of this website."

When I send an IE6.0 UA string, the message goes away, but there's still no
functionality.

No left or bottom navigation links work, except SEARCH RECORDS (bottom nav). 
There is no site map or other way to navigate the site.

I submit this as "major" because it's a government site that is supposed to
serve all citizens equally.

Reproducible: Always

Steps to Reproduce:
1. Type www.duvalclerk.com into your non-IE6 browser with a non-IE6 UA string
2. See the catastrophe
3.

Actual Results:  
I receive a message addressing all FF/Linux/Mac/Netscape/etc. users to switch to
IE6.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Government site sniffs all non-WinIE UA strings b/c site uses VBScript → duvalclerk.com - Government site sniffs all non-WinIE UA strings b/c site uses VBScript
To revisit this, the problem seems to have been cleaned up.  The code is valid now, even if semantically incorrect.  However, it now has cross-browser support.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.