are enough evidence that
and achieve complete
- 10 Aug 2008
support is easy to add (it's the same as
is not added. The problem with
is that it depends on
environment variable, that is not CGI-standard (working with the assumption that it's present cuts portability [not all webservers would implement and give the same semantics to it] and ties TWiki to CGI engine).
is not specific why TablePlugin should be aware of rewrites and I can't figure out a good reason.
- 11 Aug 2008
I added support for
. I thought about
and IMHO admins should set
and related according to their setups (with or without redirects). If we add a dependency on
variable, things will work on Apache and CGI, but there's no guarantee about other webservers and engines. So, I choose portability and standards-compliance. Waiting for feedback from TWiki community.
- 11 Aug 2008
This is one we need to discuss at a release meeting.
- 18 Sep 2008
I'll try to add support for
if the web server defined
. I hope that all web servers that support rewrite rules also defines the non-standard
(and I hope all of them use the same semantics). Probably it's fair to assume this, since
works this way.
- 04 Oct 2008
code a lot to understand
option. It takes place when
doesn't begin with
. That makes sense, except that I simply couldn't reproduce such a situation. I played with apache
a lot and always the
, I mean,
code is not executed.
Then I realized that even if I could reproduce this situation, it would not be that useful: I could generate correct links for the same script that is being executed, but not others. That's why
exist, so I generate URL's based on those settings (I also ignore
, or almost this: I use it only to set
). Those settings should be adjusted by admins considering rewrite rules.
showed a situation that this mechanism doesn't work well: TWiki is installed behind a corporate firewall. Internally it is accessed using one URL. Externally another. If I generated URLs based on
, then they would work well only for the action in use (I would correctly generate
when a topic was being viewed and correct
when being edited), that is not enough IMHO.
So I'm closing this item with this limitation, that is not only on
but also in the way TWiki generates its URLs.
A possible solution for cases like Rafael's would be to make it possible to adjust
based on the
, for example (if the internal access is made using a virtual host different from external accesses), but then it's not a bug but a feature proposal
- 05 Oct 2008