Hi, Sebastian,
Just in case. If you want recompile and test it, take these steps.
[Recompile Apache Connecotor on windows]
=========================================
1. Open VC++ studio.
2. File -> Open Workspace. It brings up file open dialog box.
3. Browse to <jrun-root>/connectors/src/apache. And change 'Files of type' of dialog
box to 'Projects(.dsp)' or 'Makefiles(.mak)' type.
4. Choose one, then open it.
Apache source tree has three files. 'apache.mak', 'apache132.mak', 'apache136.mak',
or .dsp project files.
apache.mak - generates 'apache134.dll'.
apache132.mak - generates 'apache132.dll'.
apache136.mak - generates 'apache136.dll'.
5. Add Apache includes and library to VC compiler option before compilation
- Add Apache include and library
1) Tools -> Option : it will bring up a dialog box.
2) Choose 'Directories' tab in the dialog.
3) Choose 'Platform' to Win32, and 'Shows directories for:' to 'Include files'
4) Go to the bottom of 'Directories' list and click a blank line after the last
line. It will allow to edit the blank line and give a file chooser button on righ end.
5) Browse Apache include directory. It should look like
'C:\Apache\1.3.20\include'.
If you just add these includes and compile the connector, it will fail. Need to
add Apache library module.
6) In the same dialog box, change the drop down list of 'Shows directories for:'
to 'Library files'. It will show another list in the 'Directories' list.
7) go to the bottom of the 'Directories' list and click a blank line after the
last line. And browse and choose Apache libexec directory. It should look like
'C:\Apache\1.3.20\LIBEXEC'.
8) Now close the dialog box with click 'OK'.
6. Recompile the project or Makefile.
Menu : Build -> Batch Build ...
It will bring up another small check dialog box. Check Win32 release. And click
'Build' or 'Rebuild All'.
7. A new connector 'mod_jrunXXX.dll' file can be found in
<jrun-root>/connectors/src/apache/ReleaseXXX directory.
'XXX' is going to be 132 or 134 or 136.
-----Original Message-----
From: Sebastian Millies [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 28, 2002 10:22 AM
To: JRun-Talk
Subject: Antw: RE: SSL bug in JRun web connector?
Thanks for your answer. Could you please point me at the relevant
section?
I've looked through the document, and it says only to use the
connector
wizard or connector installer, but nothing on rebuilding the
connector,
as far as I have seen.
-- Sebastian
>>> [EMAIL PROTECTED] 28.05.02 15:31:41 >>>
Rebuild the Apache connector and use the new connector. Instructions
for rebuilding the connector in JRun 3.x are included in the advanced
configuration guide.
Eric
Eric Anderson
Senior Engineer
JRun Product Support
Macromedia Incorporated
-----Original Message-----
From: Sebastian Millies [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 28, 2002 8:29 AM
To: JRun-Talk
Subject: SSL bug in JRun web connector?
Hi,
I posted this previously on the JRun newsgroups, but unfortunately
nobody had anything to say to this. Perhaps this list is interested:
I believe I have discovered a bug in the JRun web connector for
Apache.
I have successfully set up Apache 1.3.24 with SSL (I'm using mod_ssl)
and connected
both JRun 3.1 build 39664 and Tomcat 3.2.1 to it. For JRun, I'm using
the httpd.conf
entries which get created by running the connector wizard:
# JRun Settings
# JRun - Comment out this line to disable DSO (ie you compiled module
into your server.
LoadModule jrun_module
"D:/Programme/Allaire/JRun3.1/connectors/apache/intel-win/mod_jrun136.dll"
<IfModule mod_jrun.c>
JRunConfig jrun.rootdir "D:\Programme\Allaire\JRun3.1"
JRunConfig jvmlist default
JRunConfig Verbose false
</IfModule>
When requesting a URL like this:
https://my-domain/app/Snoop.jsp
(note the "https")
then request.getScheme() will incorrectly return "http".
However, when making the same request using the same Apache server but
this time
connected toTomcat, then calling request.getScheme() will correctly
return "https".
When using the JWS instead of Apache, then request.getScheme() is Ok,
too.
I conclude that mod_jrun136.dll is not passing the SSL information
correctly to JRun.
Can this be fixed by setting a directive in httpd.conf, or some JRun
property?
This is under NT 4.0 and Win2K.
-- Sebastian
--------------------------------------------------------------------------
Sebastian Millies, IDS Scheer AG
Postfach 10 15 34, 66015 Saarbrncken
Zimmer 2.34, email: [EMAIL PROTECTED]
fon +49-681-210-3221, fax +49-681-210-1311
______________________________________________________________________
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
