Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1065987 - W3C validator: Encoding of ampersand characters in URLs
W3C validator: Encoding of ampersand characters in URLs
Status: VERIFIED
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal (Show other bugs)
6.1.0
Unspecified Unspecified
unspecified Severity unspecified
: DR02
: 6.2.0
Assigned To: Lucas Ponce
Tomas Kyjovsky
:
Depends On:
Blocks: 1050065
  Show dependency treegraph
 
Reported: 2014-02-17 08:01 EST by Lucas Ponce
Modified: 2014-07-29 21:51 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
JBoss Portal produced xhtml type documents that contained URLs generated in plain-text. This caused issues with W3C validation when certain plain-text characters such as ampersands (&) in URLs were not converted to entities. The fix implements a configuration flag defined in configuration.properties (gatein.w3c.url.encoded), which allows URLs to be encoded to W3C requirements, or maintained in plain text. URLs produced by JBoss Portal can now be rendered according to W3C validation rules. The configuration flag permits the old plain-text behavior for compatibility purposes.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker GTNPORTAL-3401 Major Resolved Encoding of "&" characters in URLs. 2017-04-05 22:17 EDT

  None (edit)
Description Lucas Ponce 2014-02-17 08:01:53 EST
Description of problem:

JBoss Portal 6.1.0 produces XHTML 1.0 Strict type documents.

For a w3c validation, URLs should be encoded using html entities instead of plain "&" characters.

Version-Release number of selected component (if applicable):

6.1.0

How reproducible:

Always.

Steps to Reproduce:
1. Login into Portal.
2. Review source code generated.
3. Validate with http://validator.w3.org/ tool.

Actual results:

There are a number or URLs with plain "&" characters not compliant with XHTML 1.0 Strict type document spec.

Expected results:

URLs encoded and passing w3c validation test

Additional info:
Comment 2 Peter Palaga 2014-03-21 11:00:54 EDT
https://github.com/gatein/gatein-portal/pull/803 was merged in upstream
Comment 3 Tomas Kyjovsky 2014-05-26 12:05:33 EDT
Checked manually with homepage (anonymous) and sitemap (authenticated). Sucessfuly ran w3c validation script from Bug 1050065.

Note You need to log in before you can comment on or make changes to this bug.