Repository navigation
[JENKINS-804] API calls yield 404 for deep URLs #13827
Description
Wiki at http://hudson.gotdns.com/wiki/display/JENKINS/Remote+access+API
mentions being able to hit the api on a last stable build.
I can successfully hit the site mentioned on the wiki
http://deadlock.netbeans.org/hudson/job/trunk/lastSuccessfulBuild/api/
However, I'm running 1.136 and hitting URLs like
http://mel1u101:8080/hudson/job/customcode/lastSuccessfulBuild/api
This yields a 404, however
http://mel1u101:8080/hudson/job/customcode/lastSuccessfulBuild/
gives me the correct information.
Originally reported by nedcollyer, imported from: API calls yield 404 for deep URLs
- status: Closed
- priority: Major
- component(s): core
- resolution: Fixed
- resolved: 2007-09-11T00:10:48+00:00
- votes: 0
- watchers: 0
- imported: 2025-11-24
Raw content of original issue
Wiki at http://hudson.gotdns.com/wiki/display/JENKINS/Remote+access+API mentions being able to hit the api on a last stable build.
I can successfully hit the site mentioned on the wiki http://deadlock.netbeans.org/hudson/job/trunk/lastSuccessfulBuild/api/
However, I'm running 1.136 and hitting URLs like http://mel1u101:8080/hudson/job/customcode/lastSuccessfulBuild/api This yields a 404, however
http://mel1u101:8080/hudson/job/customcode/lastSuccessfulBuild/ gives me the correct information.
- environment:
Platform: All, OS: All
Activity
jenkins-infra-bot commentedon Sep 11, 2007
Raw content of original comment:
Fixed in 1.137. The problem is not the length of the URL, but it's just that the
remoting API was not available on all job types.