I'm not using proxy-base at all. I tried adding it, and it made things
worse. When I used a URL with the port number, it redirected to the
failed proxy pathname.
An additional bit of information: Any pathname I give (like
http://mystem/boguspath) yields the same 404 message courtesy of
CherryPy. It's as if CherryPy has taken over all web services.
As mentioned below, it works fine on another system, which I believe is
set up identically. Is there a CherryPy config file or some obscure
system setting that I should look at next?
-- Alan
Shawn Walker wrote:
Alan Steinberg wrote:
I'm trying to recreate meaningful URLs for my various repo ports, like
pkg.opensolaris.org has. On two of my systems I am able to do this
easily when I modify the httpd.conf file for apache22 using rewrite rules:
http://mysystem/release -> http://mysystem:10500
But on my main repo system, I get a "404 not found" message through the
cherrypy interface:
----
404 Not Found
The path '/release' was not found.
Powered by CherryPy 3.1.1 <http://www.cherrypy.org>
----
Any clues where to start looking? I can't find any log entries for these
errors, and the identical httpd.conf code and repo support packages
(SUNWipkg, SUNWpython-cherrypy, etc.) are installed on the different
systems.
Did you specify the --proxy-base parameter when starting the depot
server, or alternatively, set the pkg/proxy_base SMF property to
http://mysystem/release ?
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
