I get the 404, but I don't get any errors on the management pages.
I don't think that referring to mod_jk as a proxy is strictly correct. See the following for a detailed explanation.
As an aside - mod_proxy_ajp is basically mod_jk. It's just that the configuration is different (both use AJP/1.3 under the covers).
You may run into some problems if you're serving Jenkins from differing contexts. For example:
In those cases you'll probably have to do some rewriting.
I haven't done extensive Jenkins programming, so I don't know if my setup breaks for any of the use cases mentioned here:
I've also not trolled through all the pages to see if the Location header is being rewritten properly (no port 8080). However, I suspect that it is since the site works.
The only issue I'm observing is that pages representing modules in multi-module builds aren't being rendered correctly in Chrome. Much of the formatting and hyperlinks are missing. However, the same pages render correctly in Firefox. I suspect it's a Chrome vs. Jenkins issue.