Bug 184517 - HTTP bug...
Summary: HTTP bug...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: httpd
Version: 4.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Joe Orton
QA Contact:
URL:
Whiteboard:
: 184516 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-09 15:26 UTC by Nils
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-13 14:01:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nils 2006-03-09 15:26:18 UTC
Description of problem:
The problem occurs when I try to retrieve information from an internet site 
using wget or curl, or for that matter any other function that provide http 
communication.
It seems when you are trying to reach sertain internet pages the communication 
stalls up to 30 seconds.
I've testet this on many servers including RHEL3 but it only occurs with RHEL4.

Version-Release number of selected component (if applicable):

How reproducible:
The problem occurs every time, but it is dependend on which site you are 
trying to reach. With the following example, it happens every time. 

Steps to Reproduce:
1.wget http://www.itu.int/home/index.html
2.curl http://www.itu.int/home/index.html
  
Actual results:
The http communication stalls for up to 30 seconds

Expected results:


Additional info:

Comment 1 Joe Orton 2006-03-13 14:01:48 UTC
This is likely to be due to DNS problems, or general networking issues,
unrelated to the httpd package.

Please contact the Red Hat Global Support Services page on our website for
technical support options: https://www.redhat.com/support.  If you have a
telephone based support contract, you may contact Red Hat at 1-888-GO-REDHAT for
technical support for the problem you are experiencing. 

Comment 2 Joe Orton 2006-03-13 14:02:41 UTC
*** Bug 184516 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.