I have double checked and it seems to me this has been fixed about a couple of months ago (before your post). The problem is that data stored before this was fixed may contain the full path.
Can you verify the problem is fixed in 1.66.2? Massimo On Aug 23, 6:58 pm, Richard <richar...@gmail.com> wrote: > I would like to upgrade my web2py when this is fixed, so is it worth > creating an issue on Google Code to track it? > Or has it already been fixed? > > Richard > > On Aug 20, 4:26 pm, Richard <richar...@gmail.com> wrote: > > > great! > > Apparently some old versions of IE include the full path. > > > Richard > > > On Aug 19, 5:39 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > Yes, this may be a bug on windows. I will fix it. > > > > On Aug 18, 9:04 pm, Richard <richar...@gmail.com> wrote: > > > > > hello, > > > > > From an upload form should request.vars.<upload_name>.filename contain > > > > the original file basename, full path, or the raw string of whatever > > > > was in content-disposition? > > > > I had assumed it was the basename but from some error tickets found it > > > > must be the raw string. > > > > > Would it be worth parsing this variable into something consistent? > > > > On my Linux box I am occasionally getting filenames like "C:\ > > > > \Documents and Settings\\user\\Desktop\\file.txt", which can't be > > > > parsed with os.path.basename(). > > > > > Richard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
