Bob Harner wrote:
ProxyGenerator.java from Lenya 1.2_X (both released & svn versions)
has this code at line 203:
try {
url = new URL(this.source);
log.debug(".createURL(): " + url);
} catch (MalformedURLException e) {
url = new URL("http://"; + request.getServerName() + ":" +
request.getServerPort() + this.source);
log.debug(".createURL(): Add localhost and port: " + url);
} ;
Shouldn't that hard-coded http:// be request.getScheme() instead?
When I turn on debugging I get this in log4j.log:
127708 2005-11-10 16:01:30,860 [ExecuteThread: '23' for queue:
'weblogic.kernel.Default'] DEBUG
org.apache.lenya.cms.cocoon.generation.ProxyGenerator.createURL():205
- .createURL(): Add localhost and port:
http://www.mycompany.com:443/lenya/servlet/QuartzSchedulerServlet
I have Lenya 1.2.4 running under WebLogic behind a Sun web server
using WebLogic's plugin, a common WebLogic configuration. The web
server is running SSL, but WebLogic is not. Most of Lenya works fine,
except that when I publish a document an HTTP connection is made back
to the web server (why? I don't know) to a URL like this:
http://www.mycompany.com:443/lenya/servlet/QuartzSchedulerServlet
The 443 makes sense. But the http:// part doesn't. The connection
fails because the web server is expecting an HTTPS connection to 443,
not HTTP.
So I have 3 questions:
1) Is ProxyGenerator.java wrong?
yes, I think your are right. Would you like to submit a patch ;-)
2) Why does the publication process need to make an HTTP(S) connection
to the web server at all?
within src/webapp/lenya/usecase.xmap one has
<!-- Publish -->
<map:match pattern="publish" type="usecase">
<map:match pattern="showscreen" type="step">
<map:generate type="serverpages"
src="{fallback:content/publishing/screen.xsp}"/>
<map:transform
src="{fallback:xslt/publishing/publish-screen.xsl}">
<map:parameter name="use-request-parameters" value="true"/>
</map:transform>
<map:transform
src="cocoon:/notification/{../../1}/publish.xsl"/>
<!-- This transformer can cause trouble with WebLogic Server
on AIX -->
<map:transform
src="cocoon://scheduler/{../../1}/{page-envelope:area}/{../../3}.xsl"/>
<map:call resource="style-cms-page"/>
</map:match>
which means the scheduler is being called to show possible scheduled jobs
for this specific document.
Why can't it just move the files from the
authoring to the live directory and be done?
see above
3) Is there a way to control the scheme/protocol used for this
connection back to the web server?
what do you mean? Can you explain a bit more?
Thanks
Michi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
