Just my opinion... Encoded or not the Unix in me would never use a file name like main.aa<bb>cc
Even encoded I think that < and > should be not allowed as part of a file name. On Sun, Oct 18, 2009 at 11:06 AM, Hans <[email protected]> wrote: > > I've seen another page naming anomaly: > > With the changes I suggested made to the BOLTmessages() function, > I tried creating a page named main.aa<bb>cc > This failed with an error "Invalid page name. Please try again." (i > think), understandably, since i used < and >. > Then i tried again, replacing < with < and > with > > i.e. with name main.aa<bb>cc > The page got saved, with filename main.aa%26lt%3Bbb%26gt%3Bcc > but at the same time the new page did not display, instead i get an > error: missing page main.aa > It seems the redirect after submission and page save used > main.aa<bb>cc (my input), and the & in it broke the name. If it > would have used the actual name the page got saved under it would have > been able to display it. > > ~Hans > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
