Why does htsearch use “;” instead of “&” to separate URL parameters for the page buttons?
In versions 3.1.5 and 3.2.0b2, and later, htsearch was changed to use a semicolon character “;” as a parameter separator for page button URLs, rather than “&”, for HTML 4.0 compliance. It now allows both the “&” and the “;” as separators for input parameters, because the CGI specification still uses the “&”. This change may cause some PHP or CGI wrapper scripts to stop working, but these scripts should be similarly changed to recognize both separator characters. For the definitive reference on this issue, please refer to section B.2.2 of W3C’s HTML 4.0 Specification, Ampersands in URI attribute values. We’re all a little tired of arguing about it. If you don’t like the standard, you can change the Display::createURL() code yourself to ignore it. See also question 4.13.If you want to try working within the new standard, you may find it helpful to know that recent versions of CGI.
In versions 3.1.5 and 3.2.0b2, and later, htsearch was changed to use a semicolon character “;” as a parameter separator for page button URLs, rather than “&”, for HTML 4.0 compliance. It now allows both the “&” and the “;” as separators for input parameters, because the CGI specification still uses the “&”. This change may cause some PHP or CGI wrapper scripts to stop working, but these scripts should be similarly changed to recognize both separator characters. For the definitive reference on this issue, please refer to section B.2.2 of W3C’s HTML 4.0 Specification, Ampersands in URI attribute values. We’re all a little tired of arguing about it. If you don’t like the standard, you can change the Display::createURL() code yourself to ignore it. See also question 4.13.
In versions 3.1.5 and 3.2.0b2, and later, htsearch was changed to use a semicolon character “;” as a parameter separator for page button URLs, rather than “&”, for HTML 4.0 compliance. It now allows both the “&” and the “;” as separators for input parameters, because the CGI specification still uses the “&”. This change may cause some PHP or CGI wrapper scripts to stop working, but these scripts should be similarly changed to recognize both separator characters. See also question 4.13.
Related Questions
- What is the difference between the "Save as Default" and "Save Settings" buttons on the evaluation report options page?
- Why are the buttons suddenly no longer working, why does the layout of the results page look funny, etc.?
- Why does htsearch use ";" instead of "&" to separate URL parameters for the page buttons?
