You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[JENKINS-781] Search box in browser toolbar does not work in combination with URL rewriting #13821
I have Hudson running on port 2080 on the server, but am using lighttpd to
rewrite URLs so as to expose only port 80 to the outside world. Normally this
works fine, but it seems that Hudson is exposing its search engine using an
absolute URL (including host and port information). Is it possible to expose a
relative URL instead, so that after URL rewriting the Firefox search toolbar
would get the correct port (80)?
I have Hudson running on port 2080 on the server, but am using lighttpd to
rewrite URLs so as to expose only port 80 to the outside world. Normally this
works fine, but it seems that Hudson is exposing its search engine using an
absolute URL (including host and port information). Is it possible to expose a
relative URL instead, so that after URL rewriting the Firefox search toolbar
would get the correct port (80)?
I believe relative URL doesn't work inside open-search descriptor.
I modified code so that it uses the URL you configure in the system config
screen, and only use the request URL as the fall back.
Another way to solve the problem would be to use something like AJP instead of
simply HTTP request forwarding.
This change is in 1.135.
I believe relative URL doesn't work inside open-search descriptor.
I modified code so that it uses the URL you configure in the system config
screen, and only use the request URL as the fall back.
Another way to solve the problem would be to use something like AJP instead of
simply HTTP request forwarding.
Activity
jenkins-infra-bot commentedon Sep 2, 2007
Raw content of original comment:
I believe relative URL doesn't work inside open-search descriptor.
I modified code so that it uses the URL you configure in the system config
screen, and only use the request URL as the fall back.
Another way to solve the problem would be to use something like AJP instead of
simply HTTP request forwarding.
This change is in 1.135.