Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12439

Comma in configuration value causes 404 page

XMLWordPrintable

      If a option of a matrix project contains a comma in its value, the build page of that configuration shows instead a 404 error. The behavior is identical to the one described in the fixed bug 1352. It seems to have been fixed for all/most characters but not for comma.

          [JENKINS-12439] Comma in configuration value causes 404 page

          Roland Schulz created issue -

          evernat added a comment -

          Is it reproduced with a recent Jenkins version?

          evernat added a comment - Is it reproduced with a recent Jenkins version?

          Roland Schulz added a comment -

          The most recent version I have access to is 1.486. And this still has the problem.

          Roland Schulz added a comment - The most recent version I have access to is 1.486. And this still has the problem.

          Roland Schulz added a comment -

          It still occurs with 1.500.

          Roland Schulz added a comment - It still occurs with 1.500.
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-16055 [ JENKINS-16055 ]
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-24765 [ JENKINS-24765 ]
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-16486 [ JENKINS-16486 ]

          Daniel Beck added a comment -

          Still occurs on 1.580 with Matrix project 1.3.

          Daniel Beck added a comment - Still occurs on 1.580 with Matrix project 1.3.
          Daniel Beck made changes -
          Component/s New: matrix-project [ 18765 ]

          Daniel Beck added a comment -

          Unrelated to JENKINS-1352 – that one is about character set issues, this has the problem that the field separator used in the URL is also a valid field value, breaking the "URL decoder".

          Daniel Beck added a comment - Unrelated to JENKINS-1352 – that one is about character set issues, this has the problem that the field separator used in the URL is also a valid field value, breaking the "URL decoder".

            Unassigned Unassigned
            rschulz Roland Schulz
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: