1,870
edits
Changes
Jump to navigation
Jump to search
Line 7:
Line 7: − +
How to set up a secure webdav area on an Apache 2.0 server that can hold an Adobe Acrobat 8 shared review document (view source)
Revision as of 15:29, 28 August 2007
, 15:29, 28 August 2007→Problem: Acrobat 8 says "Shared Folder Location is not valid"
Having already learned how to [[How to set up a secure webdav area on an Apache 2.0 server that is mountable from windows| set up a secure webdav area on an Apache 2.0 server that is mountable from windows]] I though that it would be easy to configure my server to host Acrobat shared reviews. How wrong I was!
Having already learned how to [[How to set up a secure webdav area on an Apache 2.0 server that is mountable from windows| set up a secure webdav area on an Apache 2.0 server that is mountable from windows]] I though that it would be easy to configure my server to host Acrobat shared reviews. How wrong I was!
== Problem: Acrobat 8 says "Shared Folder Location is not valid" ==
== Problem 1: Acrobat 8 complains that "The Shared Folder Location provided is not valid" ==
The first problem I managed to solve. It complicated by the fact that the http communication is done by Acrobat behind the scenes without any way for the user to see or manage how the connection is being handled. When the connection uses ssl, how certificates are being validated and how client certificates, if any, are being selected is mysterious. I decided right away to give up on client certificates, and just try to use http basic authentication over ssl to protect my site. Even this was not easy. The reason for this was that my ssl.conf configuration for the secure portion of my web site contained the following couple of lines
The first problem I managed to solve. It complicated by the fact that the http communication is done by Acrobat behind the scenes without any way for the user to see or manage how the connection is being handled. When the connection uses ssl, how certificates are being validated and how client certificates, if any, are being selected is mysterious. I decided right away to give up on client certificates, and just try to use http basic authentication over ssl to protect my site. Even this was not easy. The reason for this was that my ssl.conf configuration for the secure portion of my web site contained the following couple of lines