Yes, actually. However, I think we may want to also filter the anchors, to ensure they are valid html names.
Let's try adding # to the escaped chars. Line 55 or so engine.php. I'm testing now, but if you are faster... Either we will want to clarify the filtering process, so it's not called twice. But sooner, not later I think... Cheers, Dan On Thu, Sep 3, 2009 at 8:28 AM, DrunkenMonk<[email protected]> wrote: > >> P.S. It may be easier to set a special line in the filtering for when >> pages are being scanned to automatically convert to url encoded. But >> then of course, everything will pass and the filtering is useless... >> On the other hand, if all page names get url encoded, perhaps we don't >> need to worry about special chars anyway. I need to check into the >> security issues again. But I suspect that third line should just read >> >> if ($page == '') return; > > That does sound like a better solution. > > I'm having trouble with [(include page#log)] right now. I wonder if > it's connected. > > I notice that boltfilter is being called twice as it stands, and that > if you put the utf2url where you suggest you may break anchor rules. > I'm going to try to remove boltfilter from that position and rely on > the second one, see if it breaks anything. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
