Bug 49743 - SSI 'echo encoding="(url/none)"' bug
Summary: SSI 'echo encoding="(url/none)"' bug
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_include (show other bugs)
Version: 2.2.15
Hardware: PC Linux
: P2 major (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2010-08-12 06:50 UTC by tjones
Modified: 2018-11-07 21:08 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tjones 2010-08-12 06:50:52 UTC
The 'echo encoding' in the Apache SSI module 'mod_include' is not working, and it somehow looks totally messed up. This bug seems to be present since many years already (some reports dating back until 2004). Many people reporting it in several forums, but obviously nobody filed a bug report yet.

http://httpd.apache.org/docs/2.0/mod/mod_include.html#element.echo

The whole encoding is not doing what it's supposed to do.

<!--#echo encoding="url" var="HTTP_REFERER" -->

The resulting URL is NOT ENCODED at all, just returned back AS IS.

However, if I DON'T WANT encoding (encoding="none") and passing a HTML encoded variable like this...

<!--#set var="title" value="&auml;&ouml;&uuml;" -->
<!--#echo encoding="none" var="titel" -->

...it is being DECODED as plain UTF-8 ! I couldn't find a way to return the original HTML encoded string. 

If I *WANT* encoding, I don't get encoding.
If I *DON'T WANT* encoding, I get decoding.

Really strange behaviour...
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:57 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.