We use TWiki at Wind River, the company I work for. However it is not visible from outside, because it is on an Intranet behind a firewall. TWiki is hosted and developed at the SourceForge web site at http://TWiki.org/. There you can surf and add/change content a to get an idea of how TWiki works. Start surfing at the WebHome topic.
TWiki is further being developed at TWiki.org, and guess what, the TWiki.Codev web serves as the tool for collaboration on that.
Copyright | © 1999-2000 Peter Thoeny, modified 05 Oct 2001 |
This URL | http://www.thoeny.com/peter/twiki/index.html |
peter@thoeny.com |
TWiki.pm
and Net.pm
, and require MIME::Base64
. I've provided the changes here both as replacement files for TWiki.pm and Net.pm, as well as unified diffs. And of course, it'd be super-swell if this made it into the main codebase.
-- VitoMiliano - 24 Feb 2002
See ProblemRenderingLocalCityTime - according to PeterThoeny the problem with the above INCLUDE is because it needs to be aware of proxies (SourceForge uses a proxy for outbound HTTP requests apparently).
Does anyone know where this sort of SourceForge setup info is documented? I had a look on sourceforge itself but it's hard to find amongst all the proxy projects...
-- RichardDonkin - 22 Mar 2002
can this issue be side-stepped by doing a Client-side include rather than a server side one?
-- SvenDowideit - 29 Mar 2002
It could, but part of the appeal of using TWiki is that just about everything dynamic is done server-side, and it doesn't depend on the client for anything other than standard HTML rendering. This is a mark of a well-designed site, in my opinion, and I'd like to see all parts of TWiki hold to this philosophy, since it allows the greatest number of users on the greatest number of platforms and clients to access and use every part of the site. Using client-side includes could cause problems with older or less feature-rich browsers.
I'm going to add outbound proxy support soon.
-- RyanFreebern - 10 Apr 2002
I've added outbound proxy support now. It was a simple process of just a few lines of changes to Net.pm -- the modified version is attached below, as well as a unified diff file suitable for patching the Dec. 1, 2001 release of Net.pm.
To use an outbound HTTP proxy with this, just add two new variables to TWikiPreferences: getUrl()
sub is actually called. Also made minor changes to socket calls to make this work under use strict
. I have tested this code in a separate test module and it connects OK to a web server, so it should work.
use MIME::Base64
, right where you need that module, subject to some tinkering for modules like Socket that create subroutines intended for use as C-style constants:
require MIME::Base64; import MIME::Base64 ();Perl will take care of not re-importing a module if you go through the same code path twice. -- RichardDonkin - 30 Aug 2002 After a bit of experiementation on SF, I have concluded that the proxy is at http://proxy.sourceforge.net:8080 M. -- MartinCleaver - 21 Dec 2002 What specifically is still needed to bring this BeijingRelease feature status up from 0% documentation? -- GrantBow - 09 Jan 2003 The only thing left is to make sure the TWikiSystemRequirements lists the correct requirements for all platforms (read Net.pm code to see if MimeBase64NowRequired for all platforms. -- PeterThoeny - 09 Jan 2003 This is done now, right? If so, that's 100% on the documentation! -- GrantBow - 28 Jan 2003 I've recently been put in the situation where I needed to use this code behind a proxy for various reasons. Given it broke (ProxiedIncludesBrokenImplementationBug) I think this page is now misleading:
Host:
header must always be included - even to hosts with no virtual hosts.
Host:
header doesn't exist in the HTTP/1.0 specs it was in common use - which is what led to the addition and requirement of specification in the 1.1 definition.
Host:
header is missing - regardless of being a 1.1'ism. (Some proxies can - they look at the network layer)
METHOD proto://fully.qualified.host/URL HTTP/version
Host:
field (which may be a problem with some servers/proxies). The lack of support for sites on non-standard HTTP ports is also an issue.
-- MichaelSparks - 09 Jul 2003
Aha. At last I found it. The proxy for SF is above, now in bold (21Dec02).
-- MartinCleaver - 09 Jul 2003
ChangeProposalForm | |
---|---|
TopicClassification | FeatureRequest |
TopicSummary | |
CurrentState | MergedToCore |
OutstandingIssues | |
RelatedTopics | |
InterestedParties | |
ProposedFor | BeijingRelease |
TWikiContributors |
I | Attachment | History | Action | Size | Date | Who | Comment |
---|---|---|---|---|---|---|---|
pm | Net.pm | r2 r1 | manage | 6.3 K | 2002-04-19 - 20:06 | UnknownUser | Support for HTTP/1.1 INCLUDE URLs and proxies |
pm | TWiki.pm | r1 | manage | 67.3 K | 2002-02-24 - 23:25 | UnknownUser | Replacement TWiki.pm for HTTP/1.1 INCLUDE URLs |
diff | TWiki20011201-Net-pm-HTTP11-URLs-Proxy-Support.diff | r1 | manage | 1.8 K | 2002-04-19 - 20:07 | UnknownUser | Net.pm unified diff for HTTP/1.1 URLs and proxies |
diff | TWiki20011201-Net-pm-HTTP11-URLs.diff | r1 | manage | 1.5 K | 2002-02-24 - 23:26 | UnknownUser | Net.pm unified diff for HTTP/1.1 INCLUDE URLs |
diff | TWiki20011201-TWiki-pm-HTTP11-URLs.diff | r1 | manage | 1.4 K | 2002-02-24 - 23:26 | UnknownUser | TWiki.pm unified diff for HTTP/1.1 INCLUDE URLs |