Bug 52038 - NameWidth works incorrectly together with Charset=UTF-8 and russian file names
Summary: NameWidth works incorrectly together with Charset=UTF-8 and russian file names
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_autoindex (show other bugs)
Version: 2.2.21
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2011-10-16 09:06 UTC by Alexei Romanoff
Modified: 2018-11-07 21:09 UTC (History)
1 user (show)



Attachments
buggy screenshot (246.98 KB, image/png)
2011-10-16 09:06 UTC, Alexei Romanoff
Details
mod_autoindex buggy config (2.79 KB, application/octet-stream)
2011-10-16 09:07 UTC, Alexei Romanoff
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexei Romanoff 2011-10-16 09:06:06 UTC
Created attachment 27788 [details]
buggy screenshot

I use Apache from Arch Linux distro. When I tried to configure mod_autoindex for browsing a directory with Russian file names, I noticed that the names are truncated incorrectly, appeared strange "?" signs in the directory listing. 
See attached screenshot, buggy places are marked by the red line.
When I set the option 'NameWidth=*', everything looks correct. No truncating - no problems.
Comment 1 Alexei Romanoff 2011-10-16 09:07:53 UTC
Created attachment 27789 [details]
mod_autoindex buggy config

Piece of config with mod_autoindex configuration.
Comment 2 William A. Rowe Jr. 2018-11-07 21:09:25 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.