php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Doc Bug #25208 Typos in the security chapter
Submitted: 2003-08-22 06:58 UTC Modified: 2003-08-23 04:40 UTC
From: lboshell@php.net Assigned:
Status: Closed Package: Documentation problem
PHP Version: Irrelevant OS: Irrelevant
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: lboshell@php.net
New email:
PHP Version: OS:

 

 [2003-08-22 06:58 UTC] lboshell@php.net 
Description:
------------
The second example included in the section `security.errors' ("Error Reporting"), goes something like this:

  <form method="POST" action="attacktarget?errors=Y&amp;showerrors=1"&debug=1">
  <input type="hidden" name="errors" value="Y">
  <input type="hidden" name="showerrors" value="1">
  <input type="hidden" name="debug" value="1">
  </form>


There's a couple of errors in the `form' tag: (a) the `&amp;' entity shouldn't be there, and (b) there is one `"' too many.

Thanks.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-08-22 07:21 UTC] davey@php.net 
Actually for XHTML/HTML Conformance, that first &amp; *should* be an &amp; and so should the the second &. 

Which brings about the question, should we start to change things like this to bring examples upto standards compliant (X)HTML? Has the decision been made whether HTML in the manual should be HTML or XHTML yet?

He is right about the extraneous " after the 1 though.

- Davey
 [2003-08-22 07:39 UTC] didou@php.net 
I have fixed the error (b) in CVS, the bug is closed now.

+1 for a XHTML compliant documentation, but this shuold be discussed on phpdocs@lists.php.net, not in a bug report ;)

didou
 [2003-08-23 04:09 UTC] goba@php.net 
Erm, using &amp; and & interchangeably in URLs is not a solution. That page should either use & or &amp; for every URL parameter. IMHO the later would be good.
 [2003-08-23 04:40 UTC] ali@php.net 
I added the XHTML entity for the ampersand in the example, as i also think an XHTML compatible doc makes sense.

I'm setting this bug-status to closed, altough this contributes to an inconsistent manual.

-ali
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Jun 15 13:01:29 2024 UTC