Certain important links don't work at: http://166.94.9.227/ldsnet/

RESOLVED EXPIRED

Status

SeaMonkey
General
RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: Greg, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1

Dear Mozilla folks!

The LDSNet (http://166.94.9.227/ldsnet/) site contains several links on the main
page that don't work with the Mozilla browser.  

I am passing this onto you in the hopes that you can help explain the problem to
the webmaster of this site (Fairfax County Virginia government, who I've already
reported the problem to) so that they can provide the necessary functionality at
this site to allow this browser to work properly for all links.

Specifically, the links that don't work on the main page of the site are:

    - Search by Zoning Application Number (ZAPS)
    - Search by Plans & Waivers Number (PAWS)
    - Search PAWS/ZAPS by Type, Date, Participant, and Location
    - ZAPS Custom Search
    - PAWS Custom Search 

When you try to use these links, you get a "HTTP/1.1 400 Bad Request" 
response.

Whatever you can do to help out would be great.  Our office is currently using 
Mozilla and we regularly have to switch to IE to access these above links.

Thank you - your help is appreciated!  Keep up the good work! 

Greg Budnik
GJB Engineering Inc.
703-401-8855

Reproducible: Always

Steps to Reproduce:
1.  Go to http://166.94.9.227/ldsnet/
2.  Click on one of the links I reference (note that not all links are bad -
only the ones that I noted in "Details" above.
3.  You then get a "HTTP/1.1 400 Bad Request" response.

Actual Results:  
You then get a "HTTP/1.1 400 Bad Request" response.

Expected Results:  
Showed a screen of data that is provided by the local county government.

I have notified the local county government of this problem as well in the hopes
that they can also provide an explanation.  If I hear anything, I'll let you know.

Comment 1

15 years ago
they all wfm Firebird 20030917, perhaps check your cookies settings, blocking
something ?
Can you try latest 1.5RC or latest 1.4.1 nightly ?

Comment 2

15 years ago
Worksforme with build 20030916 (= Mozilla 1.5rc1) on Windows NT
I see this with 1.5rc1

The questionable code is as follows
------------------------------------------------------------
<script language="javascript">
<!--
	function __doPostBack(eventTarget, eventArgument) {
		var theform = document.Form1;
		theform.__EVENTTARGET.value = eventTarget;
		theform.__EVENTARGUMENT.value = eventArgument;
		theform.submit();
	}
// -->
</script>
------------------------------------------------------------


and links such as:
------------------------------------------------------------
<a id="lbCustPaws" class="agencysize"
href="javascript:__doPostBack('lbCustPaws','')">PAWS Custom Search</a>
------------------------------------------------------------


The links in question are:
------
LDSnet Overview
Search by Zoning Application Number (ZAPS)
Search by Plans & Waivers Number (PAWS)
Search PAWS/ZAPS by Type, Date, Participant, and Location
ZAPS Custom Search
PAWS Custom Search
Building Code Services Online
Building Permits Issued
------

The javascript generates no errors but redirects
to:http://166.94.9.227/ldsnet/default.aspx
which gives the error that the reporter sees (when done through the links).

I think it might be an evangelism issue, but I guess it would be better to wait
until 1 or more people chime in.

Comment 4

15 years ago
Well, I didn't see it with 1.5RC1 in the office (build 20030916) on Windows NT [
as reported above, and yes, I know it's a Sunday today :-( ], but I can confirm
it with 1.6a (build 2003092105) on Mac OS X 10.2.6. I didn't see any errors in
the Javascript console.

If it is a regression, why did Robert see it in RC1 ?

Comment 5

15 years ago
I see this problem in trunk, 1.5rc1, 1.4 and 1.0.2 on Linux with a fresh profile.

Could someone for which the link works attach a HTTP log file please?
http://www.mozilla.org/projects/netlib/http/http-debugging.html
OS: Windows XP → All
Created attachment 131860 [details]
HTTP Log of  *problem*

Attaching a http log of the problem taking place (sorry for the extra, I tried
to trim it as much as possible by removing my home page loading.)
I'm still of the belief that this may be a JavaScript issue (see comment #3). 
Perhaps a problem with javascript and http post?

My reasoning being that if it's a networking bug... wouldn't this be pretty
widespread?

Comment 8

15 years ago
I tried to reproduce this with a cvs build from 2003/12/22. All of the links
seem to work properly. Greg, could you try this with a current version of
mozilla and see if you can still produce the problem?

Comment 9

14 years ago
Still happens in:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7a) Gecko/20040218
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8

I tried to dupe the basic items from that page to my site (apache), and it works
alright. Could it be something with mozilla+iis? Or maybe I'm just missing some
important piece from ldsnet? :S

http://www.gozer.org/test/mozilla/219867/

1078596704[80b6570]: http request [
1078596704[80b6570]:   POST /ldsnet/Default.aspx HTTP/1.1
1078596704[80b6570]:   Host: 166.94.9.227
1078596704[80b6570]:   User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
rv:1.7a) Gecko/20040218
1078596704[80b6570]:   Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1
1078596704[80b6570]:   Accept-Language: en-us,en;q=0.5
1078596704[80b6570]:   Accept-Encoding: gzip,deflate
1078596704[80b6570]:   Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
1078596704[80b6570]:   Keep-Alive: 300
1078596704[80b6570]:   Connection: keep-alive
1078596704[80b6570]:   Referer: http://166.94.9.227/ldsnet/
1078596704[80b6570]: ] 

1078596704[80b6570]: http request [
1078596704[80b6570]:   POST /test/mozilla/219867/post.php HTTP/1.1
1078596704[80b6570]:   Host: www.gozer.org
1078596704[80b6570]:   User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.
7a) Gecko/20040218
1078596704[80b6570]:   Accept: text/xml,application/xml,application/xhtml+xml,te
xt/html;q=0.9,text/plain;q=0.8,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1
1078596704[80b6570]:   Accept-Language: en-us,en;q=0.5
1078596704[80b6570]:   Accept-Encoding: gzip,deflate
1078596704[80b6570]:   Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
1078596704[80b6570]:   Keep-Alive: 300
1078596704[80b6570]:   Connection: keep-alive
1078596704[80b6570]:   Referer: http://www.gozer.org/test/mozilla/219867/
1078596704[80b6570]: ] 

Tried doing this manually, but the error is returned before I enter the Host:
header...

-(~) telnet 166.94.9.227 80
Trying 166.94.9.227...
Connected to 166.94.9.227.
Escape character is '^]'.
POST /ldsnet/Default.aspx HTTP/1.1
HTTP/1.1 400 Bad Request
Server: Microsoft-IIS/5.0
Date: Tue, 24 Feb 2004 21:09:02 GMT
Content-Type: text/html
Content-Length: 98

I dunno much about IIS, but I found a search form on microsoft.com, and if I
POST data there, IIS waits until my request has completed.

-(~) telnet www.microsoft.com 80
Trying 207.46.250.222...
Connected to origin2.microsoft.com.
Escape character is '^]'.
POST /library/toolbar/3.0/search.aspx HTTP/1.1
[waiting]
wfm using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b)
Gecko/20040222 Firefox/0.8.0+ 

(and also IE6)

--> wfm ?

Comment 11

14 years ago
I get the 400 error in Firefox 0.8 on Linux and today's nightly Mozilla build.
Summary: Certain important links don't work at: http://166.94.9.227/ldsnet/ → Certain important links don't work at: http://166.94.9.227/ldsnet/
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.