Re: [Zope-CMF] Re: VIRTUAL_URL and ACTUAL_URL (was Re: Collector Issues)
Alexander Limi wrote at 2005-12-4 20:04 -0800: >On Sun, 04 Dec 2005 10:23:25 -0800, Dieter Maurer <[EMAIL PROTECTED]> >wrote: > >> What have anchors to do with the query string? >> >> As I understand it, "anchors" (fragments in the URL) are a client >> only concept: fragments are not transfered to the server. > >Correct, but it's impossible to construct valid anchors that do not reload >the page if you do not have a working ACTUAL_URL because of Zope setting >the value to something else than the current page. > >Thus, a link like will *reload the page*, then go >to the anchor - which is clearly not desirable behaviour. Okay, I understand. But, that "ACTUAL_URL" does not contain the query string cannot be the problem because you can easily add it. Determining the real "ACTUAL_URL" is unfortunately not that easy because * HTTP allows proxies to change the URL (that's why RFC2617 transfers the uri in 'Authentication' and does not trust the request uri) * Apache's mod_proxy is often used to modify the URL to include commands for the VHM * Right at the beginning of request processing, before VHM has a change to do its job, the URL is modified by Zope (executing ":action/method" requests) * The URL is modified again during traversal -- at some point of which the VHM does its job It will not be that easy to get it right with all of these influences. Probably the most promising route would be let VHM determine "ACTUAL_URL" from "PATH_INFO" by removing/executing its commands on it. It will probably work only in standard situations (VHM in Zope route, e.g.). -- Dieter ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: VIRTUAL_URL and ACTUAL_URL (was Re: Collector Issues)
On Sun, 04 Dec 2005 07:24:36 -0800, yuppie <[EMAIL PROTECTED]> wrote: Intended or not, ACTUAL_URL was released with a specific behavior that is useful for and used by some people. You can't change the behavior of ACTUAL_URL in a non backwards compatible way just to make it more suitable for your use cases. The original use case for ACTUAL_URL was to use with anchors, and that's why it is a bug, not intentional behaviour. If you want a variable *without* the query string (which is by far a much less common use case) that's fine - but *that* should be the new variable, not the old one. It was even added in a point release, so the "changing the behaviour" isn't really a good argument. The implementation was not complete in the first version - and I filed a bug report on it. -- _ Alexander Limi · Chief Architect · Plone Solutions · Norway Consulting · Training · Development · http://www.plonesolutions.com _ Plone Co-Founder · http://plone.org · Connecting Content Plone Foundation · http://plone.org/foundation · Protecting Plone ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: VIRTUAL_URL and ACTUAL_URL (was Re: Collector Issues)
Alexander Limi wrote at 2005-12-3 14:27 -0800: > ... >Except, the implementation did not end up including the query string - >which was the whole idea in the first place, to have ACTUAL_URL be "what >is in the address bar right now", so things like anchors work (did you >know there is no proper way of getting anchors to work in virtual hosting >setups without doing three conditional tests in your template?). I have difficulties to understand the paragraph: What have anchors to do with the query string? As I understand it, "anchors" (fragments in the URL) are a client only concept: fragments are not transfered to the server. -- Dieter ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: VIRTUAL_URL and ACTUAL_URL (was Re: Collector Issues)
Hi! Alexander Limi wrote: On Sat, 03 Dec 2005 10:04:52 -0800, Andreas Jung <[EMAIL PROTECTED]> wrote: AFAIK ACTUAL_URL contains the full URL *plus* the query string. VIRTUAL_URL does not contain the query string. ACTUAL_URL was introduced on request by the Plone developers. Except, the implementation did not end up including the query string - which was the whole idea in the first place, to have ACTUAL_URL be "what is in the address bar right now", so things like anchors work (did you know there is no proper way of getting anchors to work in virtual hosting setups without doing three conditional tests in your template?). When I suggested that it should be fixed, people wanted to invent *another* variable that included the query string, and it degenerated into a "what should we name it" discussion after that. So that thing still has to be "reinvented" in Plone, which sucks. Intended or not, ACTUAL_URL was released with a specific behavior that is useful for and used by some people. You can't change the behavior of ACTUAL_URL in a non backwards compatible way just to make it more suitable for your use cases. Anyway, ACTUAL_URL supersedes VIRTUAL_URL which is only available if the Virtual Host Monster changed the URL. I can't think of any good reason to use VIRTUAL_URL instead of ACTUAL_URL. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: VIRTUAL_URL and ACTUAL_URL (was Re: Collector Issues)
On Sat, 03 Dec 2005 10:04:52 -0800, Andreas Jung <[EMAIL PROTECTED]> wrote: AFAIK ACTUAL_URL contains the full URL *plus* the query string. VIRTUAL_URL does not contain the query string. ACTUAL_URL was introduced on request by the Plone developers. Except, the implementation did not end up including the query string - which was the whole idea in the first place, to have ACTUAL_URL be "what is in the address bar right now", so things like anchors work (did you know there is no proper way of getting anchors to work in virtual hosting setups without doing three conditional tests in your template?). When I suggested that it should be fixed, people wanted to invent *another* variable that included the query string, and it degenerated into a "what should we name it" discussion after that. So that thing still has to be "reinvented" in Plone, which sucks. -- _ Alexander Limi · Chief Architect · Plone Solutions · Norway Consulting · Training · Development · http://www.plonesolutions.com _ Plone Co-Founder · http://plone.org · Connecting Content Plone Foundation · http://plone.org/foundation · Protecting Plone ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
