search

timja / jenkins-gh-issues-poc-06-18

0 stars 0 forks source link

[JENKINS-68668] Case insensitive URLs not work as expected. #6041

Open timja opened 2 years ago

timja commented 2 years ago

Hi there.
The bug has been captured, but I don't know is expected or not.
When I try to get a job nested in a folder via a direct lower-cased URL, it could return the job itself (HTTP code: 200), and sometimes(more often) Jenkins returns an error (HTTP code: 404). Fixing URL to the proper case fixes the issue.

The original name convention:

Some examples to get direct config.xml file for "job-type" Folder (XML files are cut, full versions are attached to the ticket):
https://jenkins/job/Folder1/config.xml


...

 

https://jenkins/job/folder1/config.xml


...

 

https://jenkins/job/folder1/job/Folder2/config.xml


...

https://jenkins/job/folder1/job/folder2/config.xml



Error 404 Not Found

...

System information is attached.

Probably similar issue is https://issues.jenkins.io/browse/JENKINS-67695

Originally reported by johnroe, imported from: Case insensitive URLs not work as expected.
  • status: Open
  • priority: Major
  • resolution: Unresolved
  • imported: 2022/01/10
timja commented 2 years ago

markewaite:

The stack overflow article clarifies that while the hostname portion of the URL is case insensitive, the path portion of the URL is case sensitive.

In this case, the Jenkins URL is case sensitive.

timja commented 2 years ago

JIRAUSER145345:

markewaite
Then I would like to get clarification:
why Jenkins return ok for Folder1 and folder1 if a user downcases url? Equal results as expected for both requests?.
Whan about this one? https://issues.jenkins.io/browse/JENKINS-37761

timja commented 2 years ago

markewaite:

I made a mistake. As noted in JENKINS-37761, Jenkins treats job names as case insensitive but case preserving.