Really, support of HTTPS is not really an issue unless you're not
in control of the webserver. The T1000 version of Webinator allows
you to perform the SQL UPDATE command which makes it possible to
provide indexed docs via the HTTPS instead of HTTP.
1: Alter your HTTP conf file to allow access to the "secure" docs
via localhost.
2: Use gw in the normal way to walk the secured docs via HTTP.
3: Issue the SQL command: "update html set Url='https://'+Url"
You will need a "where" clause if not all indexed docs are to be accessed
via the HTTPS: protocol. eg:
"update html set Url='https://'+Url
where Url matches "www.myserver.com/securedocs/%'"
The fact that they are PDF files makes no difference here this method
will work for any file type.
BTW: The jury is still out on whether we will allow SQL UPDATE within the
Commercial version as well, but if we do, it will be made available
in Webinator 2.