Jim Spath wrote:
I'm implementing tagging under Catalyst and want to be as
unrestrictive as possible on the tag text. As such, I allow slashes
in the tag text.
To view information on a given tag, you hit the following path:
/tag/URI_ESCAPED_TAG
Which uses the following action in the Tag
When I access the following URI:
/tag/sl%2Fashes
$tag gets set to sl instead of sl/ashes.
Apparently back in the early days of the web, a URL like that caused
problems
I ran into this a couple of weeks ago. As far as I could the development
myapp_server actually deals with everything
Hi Matt, I had considered that. I just wanted to check with the list
before I went that route.
Thanks!
- Jim
Matt Lawrence wrote:
Jim Spath wrote:
I'm implementing tagging under Catalyst and want to be as
unrestrictive as possible on the tag text. As such, I allow slashes
in the tag text.
Unfortunately I'm using lighttpd.
Carl Johnstone wrote:
When I access the following URI:
/tag/sl%2Fashes
$tag gets set to sl instead of sl/ashes.
Apparently back in the early days of the web, a URL like that caused
problems
I ran into this a couple of weeks ago. As far as I could the
I'm implementing tagging under Catalyst and want to be as unrestrictive
as possible on the tag text. As such, I allow slashes in the tag text.
To view information on a given tag, you hit the following path:
/tag/URI_ESCAPED_TAG
Which uses the following action in the Tag controller:
sub view
On 3/6/07, Jim Spath [EMAIL PROTECTED] wrote:
I'm implementing tagging under Catalyst and want to be as unrestrictive
as possible on the tag text. As such, I allow slashes in the tag text.
To view information on a given tag, you hit the following path:
/tag/URI_ESCAPED_TAG
Which uses the
On Monday 05 March 2007 14:33, Jim Spath wrote:
When I access the following URI:
/tag/sl%2Fashes
$tag gets set to sl instead of sl/ashes.
Apparently back in the early days of the web, a URL like that caused problems
with poorly written CGI scripts that blindly opened the PATH_INFO variable.
