![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
18/Mar/14 2:33 PM
|
|
Description:
|
The current core implementation does not define a proper contract for case insensitivity leading to all sorts of bugs, e.g.
JENKINS-22057
JENKINS-12607
JENKINS-3218
JENKINS-9771
JENKINS-6377
JENKINS-20125
JENKINS-18009
Also there are a lot of issues showing a fundamental misunderstanding of why Jenkins originally used a semi-case insensitive username... (hint the real reason is because windows filesystem is case insensitive)
People seem to think that user ids are case insensitive... despite
- unix logins being case sensitive
- email addresses being case sensitive (yes they are allowed to be... read the RFC... the destination server is allowed to treat them as case sensitive... though the RFC does say a polite version of "only a fool would actually do that" it is allowed by the spec, so you cannot assume that [email protected] is the same person as [email protected]... you can however assume that [email protected] and [email protected] are the same person as is [email protected] because domain names are not case sensitive)
As such, without a plugable strategy the case sensitive/insensitivity of Jenkins is fundamentally broken.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
stephenconnolly
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
