php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #16356 file() on URL may leave open socket
Submitted: 2002-03-29 20:44 UTC Modified: 2002-07-02 17:14 UTC
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: belg4mit at mit dot edu Assigned:
Status: Not a bug Package: Filesystem function related
PHP Version: 4.1.2 OS: Linux 2.4.18
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: belg4mit at mit dot edu
New email:
PHP Version: OS:

 

 [2002-03-29 20:44 UTC] belg4mit at mit dot edu
Occasionally a file("http://foobar.com") will timeout.
Subsequenetly an open socket to foobar.com in CLOSE_WAIT may persist.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-06-25 05:45 UTC] filippo at zirak dot it
it the same bug:
http://bugs.php.net/bug.php?id=17964

when a connection is not closed from server side (e.g. timeout, but it can be a ftp (without "bye") or other protocols closed with fclose and not by server itself)
it leads to a CLOSE_WAIT state (for indefinite time on server side!!!).

	Filippo
 [2002-07-02 17:14 UTC] sterling@php.net
CLOSE_WAIT is appropriate.
 [2002-07-02 19:28 UTC] belg4mit at mit dot edu
It is appropriate for PHP to not clean up after itself and
waste kernel resources? PHP should close the socket itself
once the socket is put in a CLOSE_WAIT state, such as when
a timeout occurs.
 
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Thu Jun 24 10:01:23 2021 UTC