Skip to content

[JENKINS-31871] Jenkins improperly handles single quotes in item names #21618

Closed
Bug
Closed
[JENKINS-31871] Jenkins improperly handles single quotes in item names#21618
Bug
Labels
component:coreimported-jira-issuepriority:majorresolution:fixed

Description

@jenkins-infra-bot
jenkins-infra-bot
opened on Dec 3, 2015

Jenkins does not prohibit creating of items like "Mike's test project". So you can create this item, but after that you won't be able to reliably access it.

URL path shows "Problem accessing /job/Mike/'s/%20test%project".

  • The item cannot be opened within a folder
  • Field verification does not work in the item's configuration forms
Originally reported by oleg_nenashev, imported from: Jenkins improperly handles single quotes in item names
  • assignee: fbelzunc
  • status: Resolved
  • priority: Major
  • component(s): core
  • label(s): 2.19.4-fixed
  • resolution: Fixed
  • resolved: 2016-10-15T23:59:24+00:00
  • votes: 0
  • watchers: 3
  • imported: 2025-11-24
Raw content of original issue 
Jenkins does not prohibit creating of items like "Mike's test project". So you can create this item, but after that you won't be able to reliably access it.



URL path shows "Problem accessing /job/Mike/'s/%20test%project". 


    
	
  • The item cannot be opened within a folder
    • 
	
  • Field verification does not work in the item's configuration forms
    •
  • environment: 1.625.2
1 attachment

Activity

  1. jenkins-infra-bot commented on Dec 3, 2015

    @jenkins-infra-bot
    jenkins-infra-bot
    on Dec 3, 2015
    Author
    oleg_nenashev:
    • Original comment link
    • Raw content of original comment: 
      Workaround: Specify the project naming restriction patterns to warn users about the issue (see the attached screenshot)

    Workaround: Specify the project naming restriction patterns to warn users about the issue (see the attached screenshot)

  2. jenkins-infra-bot commented on Dec 6, 2015

    @jenkins-infra-bot
    jenkins-infra-bot
    on Dec 6, 2015
    Author
    danielbeck:
    • Original comment link
    • Raw content of original comment: 
      * The item cannot be opened within a folder
      


      Cannot reproduce the problem on my system (behind Apache reverse proxy). Full project name: EXPERIMENTS/foo'br can be accessed without problem.
      


      Field verification does not work in the item's configuration forms
      


      That's because of a bug in FormValidation.CheckMethod or its use in the UI.

    * The item cannot be opened within a folder

    Cannot reproduce the problem on my system (behind Apache reverse proxy). Full project name: EXPERIMENTS/foo'br can be accessed without problem.

    Field verification does not work in the item's configuration forms

    That's because of a bug in FormValidation.CheckMethod or its use in the UI.

  3. jenkins-infra-bot commented on Dec 7, 2015

    @jenkins-infra-bot
    jenkins-infra-bot
    on Dec 7, 2015
    Author
    fbelzunc:
    • Original comment link
    • Raw content of original comment: 
      I was not able to re-produce the fact that the item with singles quotes cannot be opened within a folder. However, the Field verification is really an issue as Daniel Beck said.
      


      oleg_nenashev What Jenkins version were you using?

    I was not able to re-produce the fact that the item with singles quotes cannot be opened within a folder. However, the Field verification is really an issue as Daniel Beck said.

    oleg_nenashev What Jenkins version were you using?

  4. jenkins-infra-bot commented on Oct 15, 2016

    @jenkins-infra-bot
    jenkins-infra-bot
    on Oct 15, 2016
    Author
    scm_issue_link:

    Code changed in jenkins
    User: Felix Belzunce Arcos
    Path:
    core/src/main/java/hudson/util/FormValidation.java
    http://jenkins-ci.org/commit/jenkins/bee66ede31d45b9d0814e4a45cbf2223585817e2
    Log:
    [FIXED JENKINS-31871] Properly handle single quotes in item names (#1943)

  5. jenkins-infra-bot
    closed this as completedon Oct 15, 2016

  6. jenkins-infra-bot commented on Nov 8, 2016

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 8, 2016
    Author
    danielbeck:
    • Original comment link
    • Raw content of original comment: 
      FWIW I'd like to wait a bit longer with this change, to see whether someone/something is using the obscure feature we possibly broke.

    FWIW I'd like to wait a bit longer with this change, to see whether someone/something is using the obscure feature we possibly broke.

  7. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original is_duplicated_by from Jira: JENKINS-36832]

  8. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original is_duplicated_by from Jira: JENKINS-32366]

  9. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-36745]

  10. jenkins-infra-bot
    added
    bugFor changelog: Minor bug. Will be listed after features
    imported-jira-issue
    component:core
    priority:major
    resolution:fixed
    on Nov 24, 2025
  11. jenkins-infra-bot
    added the
    Bug
    issue type on Nov 25, 2025
  12. jenkins-infra-bot
    removed
    bugFor changelog: Minor bug. Will be listed after features
    on Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    component:coreimported-jira-issuepriority:majorresolution:fixed

    Type

    Bug

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions