|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #7343 php_read() problems : more infos
Submitted: 2000-10-19 11:25 UTC Modified: 2001-04-27 18:51 UTC
From: vincent dot negrier at mixad dot com Assigned:
Status: Closed Package: Sockets related
PHP Version: 4.0.3pl1 OS: Linux 2.2
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Bug Type:
From: vincent dot negrier at mixad dot com
New email:
PHP Version: OS:


 [2000-10-19 11:25 UTC] vincent dot negrier at mixad dot com
I think this might help :

- I'm using nonblocking sockets
- I think the old behavior was okay and I don't see the point of changing it (stop reading after CR/LF/\0 ...). Having another function (reads() ?) for this would be better ...

I think the problems comes from me using nonblocking sockets, and that php_read() IS blocking.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2000-10-22 19:56 UTC]
Same as #7341..
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Wed Feb 28 14:01:28 2024 UTC