Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Not A Defect
-
Component/s: core
-
Environment:Jenkins ver. 1.532.1 on apache-tomcat-7.0.39 on Windows 7
-
Similar Issues:
Description
When a 'File Parameter' is given a 'File Location' with forward slashes to use a subdirectory of the workspace (ex: subfolder/input.txt), the file cannot be downloaded from the build's Parameters page. A blank page appears when the links are clicked. If there are no slashes in the 'File Location' the file will download fine.
To Reproduce:
-------------
Create New Build
Check 'This Build is Parameterized'
Add 'File Parameter' with 'file location' = "subfolder/input.txt"
Save
Run Build using a text file named 'testfile.txt' as parameter.
On that Build's info page
Click Parameters
Try and download using the link
Result:
-------
URL like:
http://JenkinsBox/job/fileParameterBuild/1/parameters/parameter/subdir%2Finput.txt/testfile.txt
Leading to blank white Page
Expected Result:
----------------
Specified File Downloads
Additional Notes:
-----------------
The file DOES exist on the server:
C:\BUILD\.jenkins\jobs\fileParameterBuild\builds\2014-01-10_16-52-47\fileParameters\subdir\input.txt
Attachments
Issue Links
- is duplicated by
-
-
- Resolved
-
- is related to
-
-
- Resolved
-
Activity
Eric Anker
created issue -
| Field | Original Value | New Value |
|---|---|---|
| Component/s | core [ 15593 ] | |
| Component/s | build-with-parameters [ 17657 ] |
Do you access Jenkins through a reverse proxy?
I don't believe so. it's a single server and the issue is present on localhost. How else can I help diagnose?
Eric Anker
added a comment - I don't believe so. it's a single server and the issue is present on localhost. How else can I help diagnose? I confirm the issue on Jenkins 1.561 on CentOS 6 behind Apache reverse proxy.
... however not on a localhost. And I know my Apache reverse proxy is broken.
Eric: What version of Jenkins are you using? Is there a note complaining about your reverse proxy setup on the "Manage Jenkins" page?
Jenkins ver. 1.514 / apache-tomcat-7.0.39
No complaint on the Manage Jenkins Page
What else can I look for?
Eric Anker
added a comment - Jenkins ver. 1.514 / apache-tomcat-7.0.39
No complaint on the Manage Jenkins Page
What else can I look for? Improved reverse proxy brokenness detection was added in 1.552. If you have a way to set up a second context with a new versions to see whether it complains would be interesting to learn.
That being said, is the following relevant to your setup? http://tomcat.apache.org/connectors-doc/reference/apache.html#Forwarding
Try to set
JkOptions +ForwardURICompatUnparsed
Please report back if you get this fixed, as that'd help us improve the docs.
I'm using pure Tomcat (No Apache web server) so, I don't that Jk setting applies...
I tried upgrading to Jenkins ver. 1.554.2 and updating all the plugins on my test system - The Manage Jenkins Page has no warnings about reverse-proxy and the issue is still present.
Thank you for your continued support, Daniel.
Where should I look next?
Eric Anker
added a comment - I'm using pure Tomcat (No Apache web server) so, I don't that Jk setting applies...
I tried upgrading to Jenkins ver. 1.554.2 and updating all the plugins on my test system - The Manage Jenkins Page has no warnings about reverse-proxy and the issue is still present.
Thank you for your continued support, Daniel.
Where should I look next? I'm mostly out of ideas 
Assuming you have a Windows box around you could run Jenkins with integrated Jetty on (java -jar jenkins.war): Does the issue occur there as well (i.e. Windows/Jetty combination)?
Erik: Did you have a chance to test on a Jetty-based instance yet?
Eric Anker: Ping!
Sorry for the delay. Thanks for following up.
That scenario appears to work!
So there's something not right with my fairly stock tomcat instance then?
Eric Anker
added a comment - Sorry for the delay. Thanks for following up.
That scenario appears to work!
So there's something not right with my fairly stock tomcat instance then? Eric: Does org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH help?
http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/157941
Further reference: http://tomcat.apache.org/security-5.html#Fixed_in_Apache_Tomcat_5.5.22,_5.0.SVN
Those settings fixed it.
Thank you so much for your attention to this issue!
Eric Anker
added a comment - Those settings fixed it.
Thank you so much for your attention to this issue! Not a Jenkins issue.
Added to documentation in the wiki.
| Resolution | Not A Defect [ 7 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Jenkins IRC Bot
made changes -
| Component/s | parameters [ 15594 ] |
| Link |
This issue is duplicated by |
| Link |
This issue is related to |
| Workflow | JNJira [ 153199 ] | JNJira + In-Review [ 194505 ] |
The File Parameter is located in Jenkins core