439117 - AJAX request enties appear empty on the server

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Leonid Zaslavsky]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9) Gecko/2008052906 Firefox/3.0

NCBI tools for multiple sequence alignments and phylogenetic tree building, that are parts of The NCBI Influenza Virus Resource did not produce any results when Firefox 3 Beta was used.

Our testing showed that the request has been created on the client side and produced empty entries on the server side. The amount of entries was the same as in correct runs under other browsers.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.ncbi.nlm.nih.gov/FLU
2. Select Influenza A, any, any, 4(HA), H3N2, 1970, 1972
3. Select Full-length sequences only,
4. Remove identical sequences,
5. Sequences from the FLU project only
6. CLICK "Get sequences"
7. CLICK "Multiple alignment"
Actual Results:  
The application starts running, reports job submission and job being executed for some time, and corrupted response after some time.

Expected Results:  
Multiple alignment being produced and shown on the screen almost momentarily.

It looks like the request body is interpreted by Firefox 3 in a non-standard fashion that is not understandable to the web server.


The same problem under Windows XP and Windows Vista.

Comment 1

[Leonid Zaslavsky]

CORRECTION:

The web site in Step 1 is

http://www.ncbi.nlm.nih.gov/genomes/FLU

Comment 2

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.9 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

Comment 3

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.10 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.