Hi Stefan,
I couldn't solve this problem yet...
I have been tried a lot of configurations, but our Elog doens't work well in IE with https 
It works very well to read, list, find the messages, delete, and so on...
But all users have problems with edit and preview commands when they are using IE + https.
When we use Elog in IE without https, everything works fine. ?)
We are using :
httpd-2.0.54
Fedora Core release 1 (Yarrow)
elog-2.6.0
The redirect directive in httpd.conf:
<VirtualHost xxx.xxx.xx.xx>
ServerAdmin our.email.address
DocumentRoot /www/apache/htdocs
ServerName our.server.name
# Rules to new elog 2.6.0
Redirect / https://our.server.name:9898
ErrorLog logs/error_log
CustomLog logs/access_log common
</VirtualHost>
The proxy directives in ssl.conf:
(We used the http://midas.psi.ch/elogs/contributions/11 message like reference.
Thanks a lot for the contribution!!!  )
<VirtualHost xxx.xxx.xx.xx:9898>
# Here be standard configuration for the Virtual Host
ServerName our.server.name:9898
ServerAdmin our.email.address
RequestHeader set Front-End-Https "On"
# This be the path to the elog directory
# (This didn't seem to make any difference, but it be a good
# idea nonetheless)
DocumentRoot "/www/src/elog-2.6.0"
# Here be the setup for the SSL component of the Virtual Host
SSLEngine On
SSLCertificateFile /www/apache/conf/ssl.crt/server.crt
#SSLCertificateKeyFile /www/apache/conf/ssl.key/server.pem
SSLCertificateKeyFile /www/apache/conf/ssl.key/server.key
# Here be the setup options for the Proxy module
ProxyRequests Off
ProxyPreserveHost On
# This be the root of the new Virtual Host, and it should be
# redirected to the port the elogd server is listening to
# (8082 on our poop deck).
<Location />
ProxyPass http://our.server.name:8082/
ProxyPassReverse http://our.server.name:8082/
SSLRequireSSL
</Location>
ErrorLog /www/apache/logs/error_log
TransferLog /www/apache/logs/access_log
</VirtualHost>
And the URL is configured in elogd.cfg like your suggestion (Thanks ! )
URL = https://our.server.name:9898
The elgod.cfg is attached to this message to add more details about our configuration.
Thanks in advance.
Regards,
Elaine
| Stefan Ritt wrote: |
| Elaine Cristina Franchini dos Anjos wrote: | | I edited and used preview many times and the ELOG worked fine without errors in IE. So, I think my problem is something configured in the proxy or https that Internet Explorer doesn't work very well in this circumstance. |
Have a look at your URL = ... statement in elogd.cfg
It should probably read
URL = https://antares.ccuec.unicamp.br:9696
ELOG uses redirection internally. To determine it's own address, it uses the URL statement. If you use Apache as an proxy together with https, you have to specify the URL under which you usually access ELOG from outside. If this is wrong, ELOG might try to redirect to http:// or something which might not be possible.
A good way to debug this is to run ELOG with the -v flag and carefully watch the HTTP traffic. You will see Location: ... statements which redirect the browser, then the browser will access the redirected URL (if it's correct), or you will see nothing (in case the browser tries to access a non-existing URL). |
|