I use "complete URL", which for me is required because my library is inside the SSL domain (https://my.domain.org/library). However, I am not convinced that machine/port specification would work even without the /library. CC makes no effort to intuit the protocol from the port. It does, however, intuit the port from the protocol, which is how it knows what to do when it sees https.
I start the calibre content server with the argument "--url-prefix library".
Just in case it might be helpful, here is my apache2 config for SSL connections to the library. I left out all the cruft to set up the certs.
Code:
# Ebook Library CALIBRE https
<Location "/library">
AuthType Digest
AuthName "Library"
AuthDigestDomain /
AuthDigestProvider file
AuthUserFile ......./library_digest_pw.txt
Require valid-user
</Location>
RewriteEngine on
RewriteRule ^/library/(.*) http://127.0.0.1:9192/library/$1 [proxy]
RewriteRule ^/library http://127.0.0.1:9192 [proxy]
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
and for completeness the arguments for calibre server
Code:
DAEMON_ARGS="--with-library $CONTENT --pidfile=$PIDFILE --daemonize -p 9192 --max-opds-ungrouped-items=200 --url-prefix /library"