10 Jun
2008
10 Jun
'08
4:48 p.m.
Hi list,
I wonder if someone has implemented a permalink for Pier, because if I have
a link like this
http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks…
I could make a permalink like this:
http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks…
Which is:
a) changing all the "+" for a "%20"
b) and erasing from "?" to the end of the string
And the (new) generated URL does work and it's shareable with others
browsers/people. If not, where should I put this to "pre" generate
permalinks for all pages, and show them properly (like the one in the image
http://i296.photobucket.com/albums/mm197/evaklo/permalink.png )?
Thanks for your time,
Lautaro Fernández
--
Luke LAut SkyFernadezWalker
10 Jun
10 Jun
7:49 p.m.
I wonder if someone has implemented a permalink for
Pier, because if
I have a link like this
http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks…
This is actually a permalink. There is some noise after the ? that you
can ignore. If people bookmark the link or send it around, that's no
problem.
I could make a permalink like this:
http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks…
This is the same permalink as above.
Which is:
a) changing all the "+" for a "%20"
b) and erasing from "?" to the end of the string
a) As far as i know, this modification doesn't change anything about
the link, it is just a different encoding. The resulting URL is the
same.
b) As long as you only remove the _s, _k, _n and [0-9]+ keys that
doesn't change anything, you will only loose the session information.
The blog component actually does something like that to display a
nicer link.
And the (new) generated URL does work and it's
shareable with others
browsers/people. If not, where should I put this to "pre" generate
permalinks for all pages, and show them properly (like the one in
the image http://i296.photobucket.com/albums/mm197/evaklo/permalink.png
)?
Doing absolutely clean URLs is possible, however it requires some
heavy Seaside hackery to avoid loosing functionality. Unfortunately my
time working on Pier is very limited at the moment.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
11 Jun
11 Jun
1:54 a.m.
Hi Lukas,
2008/6/10 Lukas Renggli <renggli(a)iam.unibe.ch>ch>:
Sorry to disagree with you, but that link isn't shareable (the one which has
the "+" instead of the "%20"). Now I'm at home, and if I click it
I got the
following error:
*Error: "/seaside/go/pier/Wiki/Smalltalks+servers" not found.*
So there must be a problem with Seaside or maybe Pier. The URL I can see
after clicking is:
http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks…
Notice that the "+" has changed into a "%2B", which is a "+"
in ASCII code,
and it seems that Pier can't process it in a good way. That is because the
page name isn't "Smalltalks+servers", actually is "Smalltalks
servers".
This link (with the %20) is showed properly here, in my home.
Do you think that my installation of Pier (or maybe Seaside) isn't working
well?
But if you insert a link like this:
http://yourHost:aPort/seaside/go/pier/Wiki/Talks
, the part of "/pier/Wiki/Talks" is traceable, so if you click
http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Talks you
will be able to see the "Talks" page in Pier.
Isn't this an absolutely clean URL for the "Talks" page?
Cheers,
[...]
http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks…
This is actually a permalink. There is some noise after the ? that you
can ignore. If people bookmark the link or send it around, that's no
problem. I could make a
permalink like this:
http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks…
This is the same permalink as above. Which is:
a) changing all the "+" for a "%20"
b) and erasing from "?" to the end of the string
a) As far as i know, this modification doesn't change anything about
the link, it is just a different encoding. The resulting URL is the
same.
b) As long as you only remove the _s, _k, _n and [0-9]+ keys that
doesn't change anything, you will only loose the session information.
The blog component actually does something like that to display a
nicer link.
And the (new) generated URL does work and
it's shareable with others
browsers/people. If not, where should I put this to "pre" generate
permalinks for all pages, and show them properly (like the one in
the image http://i296.photobucket.com/albums/mm197/evaklo/permalink.png
)?
Doing absolutely clean URLs is possible, however it requires some
heavy Seaside hackery to avoid loosing functionality. Unfortunately my
time working on Pier is very limited at the moment. Lukas
Thanks in advance for your answers,
Lautaro Fernández
--
Luke LAut SkyFernadezWalker
7:58 a.m.
So there must be a problem with Seaside or maybe Pier.
The URL I can
see after clicking is:
http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks…
Notice that the "+" has changed into a "%2B", which is a
"+" in
ASCII code, and it seems that Pier can't process it in a good way.
That is because the page name isn't "Smalltalks+servers", actually
is "Smalltalks servers".
I only realize now that you are on VisualWorks. Looks like a bug in
the request parsing and URL decoding there. It works without problems
in Squeak, no matter if I use + or %20 in my URLs.
But if you insert a link like this:
http://yourHost:aPort/seaside/go/
pier/Wiki/Talks , the part of "/pier/Wiki/Talks" is traceable, so
if you click http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Talks
you will be able to see the "Talks" page in Pier.
Isn't this an absolutely clean URL for the "Talks" page?
Yes, it is.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
8:25 a.m.
2008/6/11 Lukas Renggli <renggli(a)iam.unibe.ch>ch>:
http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Smalltalks…
Ok, thanks. I'll try to find the way to fix this.
=] Thanks,
Lautaro
So there must
be a problem with Seaside or maybe Pier. The URL I can
see after clicking is:
Notice that the "+" has changed into a
"%2B", which is a "+" in
ASCII code, and it seems that Pier can't process it in a good way.
That is because the page name isn't "Smalltalks+servers", actually
is "Smalltalks servers".
I only realize now that you are on VisualWorks. Looks like a bug in
the request parsing and URL decoding there. It works without problems
in Squeak, no matter if I use + or %20 in my URLs.
But if you insert a link like this:
http://yourHost:aPort/seaside/go/
pier/Wiki/Talks , the part of "/pier/Wiki/Talks" is traceable, so
if you click
http://neuquina.lifia.info.unlp.edu.ar:8011/seaside/go/pier/Wiki/Talks
you will be able to see the "Talks"
page in Pier.
Isn't this an absolutely clean URL for the "Talks" page?
Yes, it is.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
Luke LAut SkyFernadezWalker
3:17 p.m.
>>>> "Lukas" == Lukas Renggli
<renggli(a)iam.unibe.ch> writes:
Lukas> I only realize now that you are on VisualWorks. Looks like a bug in
Lukas> the request parsing and URL decoding there. It works without problems
Lukas> in Squeak, no matter if I use + or %20 in my URLs.
From the very early days in the web, + and %20 have
been considered
interchangeable in a URL. However, it's an easy part of the
spec to overlook,
or an easy thing not to know if you haven't been around since the early days.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
5792
days inactive
5793
days old
5 comments
3 participants
participants (3)
-
Lautaro Fernández -
Lukas Renggli -
merlyn＠stonehenge.com