Archives Search Engine

Body:
Subject:
From:
(email address of poster)
List:
(limit search to one mailing list)
Date:
(e.g. 10 Jun 2005, Jun 2005, or 2005)
   Search tips

Searching for: +path:freepages-advanced +(+date:apr +date:2007)
Viewing 1-21 of 21 matches from 36,127,719 documents
1. Re: [FP-ADVAN] FM vs Filenames: Experiment results! [1]
Judy Florian wrote in part: > Computer Specs: > WindowsXP > Internet Explorer 6.0 > Frontpage 2000 FrontPage is a MicroSoft application and probably is built on top of IE. So it seems thus far that MS products (IE and FrontPage) are the only failures. re folders: Interesting bit of research there, Judy. Using FM on FireFox, I was able to create a "New Folder", navigate about and populate it with no problems -- even with spaced filenames. Likewise using FM on IE, except that files with spaces in the
2. Re: [FP-ADVAN] Unable to ftp [1]
I thought that Judy was simply trying out a way of triggering the server to reject her file, so that the person she was helping would better understand why their file was triggered. As I read it Judy was being helpful and not uploading one of her files with an error. Best wishes, Jill http://goldenridge-genealogy.co.uk SEO Work page: http://goldenridge-genealogy.co.uk/about-our-site.htm -----Original Message----- From: freepages-advanced-bounces@rootsweb.com [mailto:freepages-advanced-bounces@rootsweb.c
3. Re: [FP-ADVAN] FM vs Filenames: Experiment results! [1]
Now we're getting somewhere! Using a nifty tool called Fiddler (http://www.fiddlertool.com/fiddler/) I have ascertained that FM (on MSIE) does not even interact with the RW host when there is a blank in the filename to be uploaded. It goes straight to the fetch of the error page. Obviously, any error that has been detected, happens on the client (user) PC. When a file with no spaces is uploaded (on MSIE or FireFox), the internet transaction to upload the page is easily seen. -R.
4. Re: [FP-ADVAN] Unable to ftp [1]
Here we go again! :o( Pat Asher wrote: > At 02:23 PM 4/4/2007, Rod Dav4is wrote: > >> I should add that my guess is that her uploading problems were the >> result of a bug in her FTP client, or her misuse of that program. I have >> never had a problem, using FTPx or the RW FileManager. To be certain of >> my facts, I just used the RW FileManager to (again!) upload to the >> "nonce" directory previously mentioned, the file "a.B,b.c.txt". No >> problem. > > > Rod, > > You are confusing "reserved" character
5. Re: [FP-ADVAN] Unable to ftp [1]
Judy Florian wrote > ... > Tonight I took that page, did save as, and named it aldous_to,allan > no space, just the replacement of one underscore with one comma. > > This was rejected... message on the problem was File Accept on Server. This is what you would expect to happen. The comma may be OK in file names on the server, but it's not in the rules for a legal URL. -- Glenn Holliday holliday@acm.org
6. Re: [FP-ADVAN] Unable to ftp [1]
The problem is /not/ with RW servers. Here is a directory ON RW with a comma in the name of one of the files: http://freepages.genealogy.rootsweb.com/~dav4is/test/nonce/ The file name is "a.B,b.c.txt" -R. Judy Florian wrote: >I just did an experiment to my PAGenWeb on RW account on the issue of file >accept on RW specifically. > >I had a page named aldous_to_allan which was already successfully uploaded >weeks ago. > >Tonight I took that page, did save as, and named it aldous_to,allan >no space, just
7. Re: [FP-ADVAN] FM vs Filenames: Experiment results! [1]
I would sure like to see some adventurous soul give this a try using FireFox or Opera -- or any browser other than MSIE! ;o) http://freepages.folklore.rootsweb.com/~dav4is/make-space.html -R.
8. Re: [FP-ADVAN] Unable to ftp [1]
Patricia Geary wrote: > Replies are inline- > > >> 2. Characters in file names. Submitters who are used to using commas >> in names on WinXP send me files with lots of commas (and spaces). I have to >> double-check each to make sure I re-named every file. The only characters >> allowed at - hyphen or _ underscore. Double periods before an extension on >> jpgs (as sent to me) would not upload. >> The advice to be cautious is good, but I'm just checking a point or two here ... The characters allo
9. [FP-ADVAN] Validation Problem [1]
http://homepages.rootsweb.com/~imfa/home.html Server: Apache/2.0.52 (CentOS) The character encoding specified in the HTTP header (utf-8) is different from the value in the element (iso-8859-1). I will use the value from the HTTP header (utf-8) for this validation. http://freepages.misc.rootsweb.com/~gearyfamily/revised-home.html Server: Apache/1.3.33 (Unix) mod_gzip/1.3.19.1a Validates with no qualifiers I'm still trying to figure out the validation problem on this page. Exact same page on two
10. Re: [FP-ADVAN] Unable to ftp [1]
Apparently this did not make the List. -----Original Message----- From: Jill Muir [mailto:jill@shottle.plus.com] Sent: 04 April 2007 07:12 To: 'Rod Dav4is' Cc: 'Judy Florian'; 'holliday@acm.org' Subject: RE: [FP-ADVAN] Unable to ftp Rod, Just maybe I was hinting that personally I had had enough of the subject - 8 now mine 9 messages on the same subject can be pretty boring to those on Digest mail and Dial-up. I suggest that Judy was being helpful, the person was helped and that we now drop this theme. T
11. Re: [FP-ADVAN] Unable to ftp [1]
BUT, the fact remains that - for whatever reasons - these file names ARE rejectted - whether by RW or the FTP program is really neither here nor there. If an ftp won't "go," that's ultimately a frustrating problem for the webmaster. Taken further, if a page won't ftp because the server closes the connection -- and points to a specific filename with these characters (as it does for me) -- ultimately that affects the user :: If a page cannot be ftp'd, users will never see it. Therefore, whether we use the
12. Re: [FP-ADVAN] Unable to ftp [1]
At 02:23 PM 4/4/2007, Rod Dav4is wrote: >I should add that my guess is that her uploading problems were the >result of a bug in her FTP client, or her misuse of that program. I have >never had a problem, using FTPx or the RW FileManager. To be certain of >my facts, I just used the RW FileManager to (again!) upload to the >"nonce" directory previously mentioned, the file "a.B,b.c.txt". No problem. Rod, You are confusing "reserved" characters with disallowed/invalid characters. The dot/period is obviously
13. Re: [FP-ADVAN] Validation Problem [1]
At 12:42 PM 4/5/2007, Hugh Watkins wrote: >I must admit Pat I have given up on validation > >if it looks OK in MS IE7 on WInXP sp2 > I don't bother spending time on validation for the other browsers sake > >really a matter of choosing priorities and being pragmatic ========snip============ Since on the majority of my sites, I have quite a few users of browsers other than IE, I cannot agree with you. I want the site to at least render in all browsers and looking at pages that have problems, if the pag
14. Re: [FP-ADVAN] Unable to ftp [1]
Hi, My comments interspersed, below... Glenn Holliday wrote: >Rod Dav4is wrote: > > >> But it is in the rules. So-called special characters, such as >>comma, need to be coded as "percent" escapes. Replace the comma (in >>the URL) with "%2C". >> It's all right there in the rules for coding URLs. >>http://www.ietf.org/rfc/rfc2396.txt (section 2.4.1 Escaped Encoding). >> >> I don't advocate the use of such strange file names, but I draw >>the line at calling them "invalid". They are NOT
15. Re: [FP-ADVAN] Unable to ftp [1]
Jill Muir wrote: >Apparently this did not make the List. > > > Well, I tried to steer this topic off the list, but some folks aren't having it! This was my private reply to Jill -- and will be my last posting on-list of this topic. (The people say "hallelujah"!) ;o) %%%%%%%%% These last messages have been "off-list". Judy may have been /trying/ to be helpful but, by concocting new rules (that the file names are "invalid"), she is spreading misinformation. This is something that must not go u
16. Re: [FP-ADVAN] Unable to ftp [1]
Firstly, I have never had a problem uploading such files to that RW demo folder, using both FTPx and RW's own FileManager. How do you suppose they got there? If you are having an upload problem with that "comma file", I would say that that your FTP client is suspect -- or your use of it. FTPx handles it just fine. Secondly, this being the Freepages-Advanced list -- and I emphasize advanced -- technical accuracy trumps semantics. We should not label something as invalid merely because it is a "
17. Re: [FP-ADVAN] Unable to ftp [1]
I just did an experiment to my PAGenWeb on RW account on the issue of file accept on RW specifically. I had a page named aldous_to_allan which was already successfully uploaded weeks ago. Tonight I took that page, did save as, and named it aldous_to,allan no space, just the replacement of one underscore with one comma. This was rejected... message on the problem was File Accept on Server. If you do your own experiment, you will find which characters are NOT accepted on RW. These same characters are val
18. Re: [FP-ADVAN] Unable to ftp [1]
Rod Dav4is wrote: > But it is in the rules. So-called special characters, such as > comma, need to be coded as "percent" escapes. Replace the comma (in > the URL) with "%2C". > It's all right there in the rules for coding URLs. > http://www.ietf.org/rfc/rfc2396.txt (section 2.4.1 Escaped Encoding). > > I don't advocate the use of such strange file names, but I draw > the line at calling them "invalid". They are NOT invalid -- merely > difficult to deal with. When you do the encoding, the co
19. Re: [FP-ADVAN] FM vs Filenames: Experiment results! [1]
Computer Specs: WindowsXP Internet Explorer 6.0 Frontpage 2000 Process used: In Frontpage2000 1. A normal folder was created, but one with a space - "test space" folder. 2. A normal web page with only bare bones html (body, html tags) was created BUT it was named with NO spaces. "test_space" page. 3. MS FP2000 error dialogue box says: This FTP server doesn't support folder names that contain spaces. Rename the source web's folder corresponding to "Test Space" and any other folders that have spaces in t
20. [FP-ADVAN] FM vs Filenames: Experiment results! [1]
Pat's insistence that FileManager cannot handle files with spaces in their names and my contrary experience led me to perform some experiments. The bottom line: FM running on IE /cannot/ upload such files, but it /can/ do so with every other browser I tried -- except for an apparent bug in OB1. The details of the procedure I used are here: http://freepages.folklore.rootsweb.com/~dav4is/make-space.html The details of my results: * My system: Windows XP home build 2600 (SP2) * The dir
21. Re: [FP-ADVAN] Unable to ftp [1]
But it is in the rules. So-called special characters, such as comma, need to be coded as "percent" escapes. Replace the comma (in the URL) with "%2C". It's all right there in the rules for coding URLs. http://www.ietf.org/rfc/rfc2396.txt (section 2.4.1 Escaped Encoding). I don't advocate the use of such strange file names, but I draw the line at calling them "invalid". They are NOT invalid -- merely difficult to deal with. -R. Glenn Holliday wrote: >Judy Florian wrote > > >> ... >>Ton
Viewing 1-21 of 21 matches from 36,127,719 documents

CPU seconds used 0.419937