|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #18843 Search Result flaw
Submitted: 2002-08-10 08:20 UTC Modified: 2002-12-14 10:48 UTC
From: patric at liefdeis dot com Assigned:
Status: Not a bug Package: Website problem
PHP Version: 4.2.2 OS:
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.
Block user comment
Status: Assign to:
Bug Type:
From: patric at liefdeis dot com
New email:
PHP Version: OS:


 [2002-08-10 08:20 UTC] patric at liefdeis dot com
I was searching for 'case sensitive', and saw this in the fopen() manual (in search result, that short part of the file):

If filename begins with "">case sensitive), an HTTP 1.0

But when you open the file, it says:

 If filename begins with "http://" (not case sensitive), an HTTP 1.0

With other words, the Search Engine likes rewriting 

http://" (not 



For no reason at all! It is kind of enoying :)


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2002-12-14 10:48 UTC]
The "not" word was there in a previous version of the documentation (indexed by the search engine). The #AEN... part is simply the nearest anchor in the document upwards, so if you click on the word in the search result, you get to the nearest part of the page... => This is not a bug...
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Wed Dec 07 03:05:52 2022 UTC