Request: INCLUDE URL With https Protocol

TWiki currently supports an INCLUDE of URLs with http protocol only. TWiki should support the https protocol as well it is often used in a corporate environment.

This feature should not raise the required environment.

Related: IncludeAttachmentWithHttps allows already the inclusion of attachments with https protocol.

-- PeterThoeny - 09 Nov 2004

Also related:

CannotInlineFromHttpS

NeedIncludeHttpsUrl

-- VickiBrown - 19 Nov 2004

When I talk to other Perl programmers, they all say "If I were working on this problem,, I'd convert the function to use LWP and go from there". Another programmer at my Company said the same thing, adding "It shouldn't take more than a day"

Well, probably, but that doesn't allow for testing. Nor does it allow for the fact that TWiki explicitly tries not to rely on LWP being present (see: UseLWPgetURL ) which implies that a clean solution would, at the very least, need to check for LWP and use the Sockets library iff LWP is not found.

Help!

-- VickiBrown - 16 Dec 2004

I think that we should probably use LWP if it is present, and perhaps bundle it with TWiki so it's easily accessible.

-- RichardDonkin - 17 Dec 2004

I would agree with Richard; the moral equivalent of an #ifdef LWP would greatly enhance the user experience. Bundling would be even better (but might be unacceptibly large??)

-- VickiBrown - 03 Jan 2005

If we go with LWP, we should also check to make sure Crypt::SSLeay is installed, otherwise LWP will return an "unsupported protocol" error; LWP can be installed without that module, but it will use it if present. Crypt::SSLeay is a compiled module, so it can't be bundled with TWiki.

-- PeterNixon - 08 Jul 2005

I've posted a quick hack on the INCLUDEurlDoesNotWorkWithSSL page that works in my particular case -- it does not support usernames and passwords in https:// URLs but will handle non-auth https:// URLs with standard and non-standard ports

-- ChristopherTracy - 19 Mar 2006