Zope internally constructs URLs which can get very long and very redundant. I have one example in the logs now -- /A/B/C/C/C/C/C/C/C/D/ where the C's are completely redundant. How does this happen and what, if anything, can be done to minimize the problem? (I know this has been discussed on the list before, but a quick google didn't turn up anything...)
Sorry Mark, Replied to the wrong email and hit the wrong button:-) Do you refer to your links as ./c/d or just c/d? The former will cause it to loop. I had the same problem. dropping the ./ fixed it. Michael On Mon, 2002-09-23 at 14:36, Dennis Allison wrote:
Zope internally constructs URLs which can get very long and very redundant. I have one example in the logs now --
/A/B/C/C/C/C/C/C/C/D/
where the C's are completely redundant. How does this happen and what, if anything, can be done to minimize the problem? (I know this has been discussed on the list before, but a quick google didn't turn up anything...)
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Michael Lewis writes:
Replied to the wrong email and hit the wrong button:-)
Do you refer to your links as ./c/d or just c/d? The former will cause it to loop. I had the same problem. dropping the ./ fixed it. I do not want to believe that:
"./c/d" and "c/d" are equivalent. Both can lead to URL growth... Dieter
On Tue, 2002-09-24 at 13:21, Dieter Maurer wrote:
Michael Lewis writes:
Replied to the wrong email and hit the wrong button:-)
Do you refer to your links as ./c/d or just c/d? The former will cause it to loop. I had the same problem. dropping the ./ fixed it. I do not want to believe that:
"./c/d" and "c/d" are equivalent.
Both can lead to URL growth...
Dieter
Some growth yes, but not looping through the same folder repeatedly.
[Dennis Allison]
Zope internally constructs URLs which can get very long and very redundant. I have one example in the logs now --
/A/B/C/C/C/C/C/C/C/D/
where the C's are completely redundant. How does this happen and what, if anything, can be done to minimize the problem? (I know this has been discussed on the list before, but a quick google didn't turn up anything...)
I think they refer to this as: base href madness ;-) I don't know a good, general solution, but that term might help you do a google search. Cheers, // mark
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Dennis Allison Sent: Monday, September 23, 2002 1:36 PM To: zope@zope.org Subject: [Zope] url growth
Zope internally constructs URLs which can get very long and very redundant. I have one example in the logs now --
/A/B/C/C/C/C/C/C/C/D/
where the C's are completely redundant. How does this happen and what, if anything, can be done to minimize the problem? (I know this has been discussed on the list before, but a quick google didn't turn up anything...)
You have a relative link that essentially returns itself. Some robot is chasing it down. Try not to use relative links. It is much better to do the zope thing: get the object, then ask it to spit out its absolute url: <dtml-var expr="mypage.absolute_url()">
Dennis Allison writes:
Zope internally constructs URLs which can get very long and very redundant. I have one example in the logs now --
/A/B/C/C/C/C/C/C/C/D/
where the C's are completely redundant. How does this happen and what, if anything, can be done to minimize the problem? (I know this has been discussed on the list before, but a quick google didn't turn up anything...) You want to search the mailing list archives ;-)
The issue has been discussed several times. You will find a (rude and dangerous) hack to prevent the URL growth. Dieter
participants (5)
-
Charlie Reiman -
Dennis Allison -
Dieter Maurer -
Mark McEahern -
Michael Lewis