If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Frequent network timeouts when ever i submit information

RESOLVED INCOMPLETE

Status

()

Core
Networking
--
major
RESOLVED INCOMPLETE
9 years ago
7 years ago

People

(Reporter: Jamesvernon, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.18) Gecko/20081029 Firefox/2.0.0.18 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.18) Gecko/20081029 Firefox/2.0.0.18 (.NET CLR 3.5.30729)

Whenever i submit a post or thread to forum, i get a network timeout. 

This does not happen on 2.0.18, and there for, i use that. But everytime i upgrade to FF3, this happens everywhere.

Reproducible: Always

Steps to Reproduce:
1. Write to posts a thread/post/comment
2. Click submit
3. Network error
Actual Results:  
Network timeout.

Expected Results:  
Loaded the page with the post added
Component: Build Config → Networking
Product: Firefox → Core
QA Contact: build.config → networking
What is evidence that your problem is caused by Tb's flaw in code?
What is your base that your problem is caused by Tb's flaw in code?
Have you searched bugzilla.mozilla.org well before open your new bug report? (including DUP'ed or WONTFIX'ed or INVALID'ed bugs)
Please note that here is bugzilla.mozilla.org, not support forum.

Have you read MozillaZine Knowledge Base articles such as following?  
> http://kb.mozillazine.org/Firewalls
No problem when non-POST access? (e.g. no problem when access to www.google.com, www.yahoo.com etc.)

If you need help, ask help at support forum such as MozillaZine forum first, please.
no response, so => incomplete
if you still see this problem or have a more detailed description of how the issues is resolved, please comment in the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.