Scoop -- the swiss army chainsaw of content management
Front Page · Everything · News · Code · Help! · Wishlist · Project · Scoop Sites · Dev Notes · Latest CVS changes · Development Activities
Tiny bug with URL decoding Bugs
By fluffy grue , Section Code []
Posted on Sun Jan 13, 2002 at 12:00:00 PM PST
Seems that scoop doesn't properly decode the + symbol in a URL. According to the appropriate standards, a space can be represented in a URL by either a + or a %20, and a lot of older webbrowsers actually do favor a + over %20.

Of course, there's always the possibility that this bug is actually in mod_rewrite. :D
< Annoucing Dialognow.org | Coexistant Scoop site >

Menu
· create account
· faq
· search
· report bugs
· Scoop Administrators Guide
· Scoop Box Exchange

Login
Make a new account
Username:
Password:

Related Links
· Scoop
· a +
· a %20
· More on Bugs
· Also by fluffy grue

Story Views
  33 Scoop users have viewed this story.

Display: Sort:
Tiny bug with URL decoding | 8 comments (8 topical, 0 hidden)
Incidentally (none / 0) (#1)
by fluffy grue on Sun Jan 13, 2002 at 08:27:10 PM PST

After further exploration, it looks like even modern browsers use +s for form submission, but it's only in the rewrite rules that things are breaking; the non-rewritten URL works just fine, even though it involves a + for the space character.
--
(λq.qq)(λq.qq)


Not fixable, I think (none / 0) (#3)
by panner on Wed Jan 16, 2002 at 02:23:32 PM PST

First off, new URLs don't use mod_rewrite at all. All of it is done internally. And now on to the comment I wrote before realizing I hadn't mentioned this:

I checked, Scoop doesn't do any of that escaping. Apparently, when Apache gets the request, it does the decoding and stores the decoded one in r->uri, which makes sense. It also keeps the original in r->unparsed_uri.

Scoop uses the URI, and mod_perl apparently doesn't offer access to the unparsed one. So we can't just add decoding of + to space (well, we could, but then real plus signs would get caught too). This is also why names with slashes in them are such problems: even though those slashes are encoded in the request, Apache decodes them, and then Scoop can't tell the difference.

The reason older URLs work is that the parsing of that is handled by Apache::Request, which knows what to do with the plus sign, and works with something Apache hasn't already messed with.

So, as of now, I don't know of any way to fix this that wouldn't end up breaking something else.



--
Keith Smiley



peterstrong (none / 0) (#7)
by peterstrong on Mon Jun 27, 2016 at 11:06:44 AM PST

If we can only encounter each other rather than stay with each other 192.168.1.1 192.168.1.1 192.168.1.1 192.168.1.1



best construction company NYC (none / 0) (#8)
by Pervez on Sun Mar 31, 2019 at 01:08:38 PM PST

Love with all your good positioning! When I relished reviewing the product; you're a wonderful document article author. I must really encourage people continue one's beneficial do the trick. Here press in this article best construction company NYC Employ a satisfying time!



Tiny bug with URL decoding | 8 comments (8 topical, 0 hidden)
Display: Sort:

Hosted by ScoopHost.com Powered by Scoop
All trademarks and copyrights on this page are owned by their respective companies. Comments are owned by the Poster. The Rest © 1999 The Management

create account | faq | search