Zoe: Captain will come up with a plan. Kaylee: That's good. Right? Zoe: Possibly you're not recalling some of his previous plans.

'Safe'


Buffistas Building a Better Board  

Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.

To-do list


Am-Chau Yarkona - Mar 25, 2003 1:53:35 pm PST #3598 of 10000
I bop to Wittgenstein. -- Nutty

IIRC, at some point this was discussed and it was considered that URLs didn't have apostrophes in them. Back in this thread quite some way. Would that be what's causing this problem?


Jon B. - Mar 25, 2003 1:55:30 pm PST #3599 of 10000
A turkey in every toilet -- only in America!

Thanks Hil. Since when are apostrophes allowed in URLs? I'm going to be a snob and say that our code is fine; the URL should change. I dislike spaces in URLs too. Those %20's drive me nuts.


Betsy HP - Mar 25, 2003 1:56:41 pm PST #3600 of 10000
If I only had a brain...

I've certainly never seen a URL with an apostrophe in it before, but I'm too zonked to go check the standard.


Betsy HP - Mar 25, 2003 1:58:29 pm PST #3601 of 10000
If I only had a brain...

I lied.

Apostrophes are legitimate in URLs.

[link]


Jon B. - Mar 25, 2003 2:03:25 pm PST #3602 of 10000
A turkey in every toilet -- only in America!

Thanks for the research Betsy. I still don't like 'em because they're going to cause trouble in places. Not just here. Why take the chance?


Betsy HP - Mar 25, 2003 2:21:21 pm PST #3603 of 10000
If I only had a brain...

Because they are legal in URLs, which means that people will post URLs containing them. We don't control the content or format of URLs.


Jon B. - Mar 25, 2003 2:24:00 pm PST #3604 of 10000
A turkey in every toilet -- only in America!

We don't control the content or format of URLs.

Yeah, I get that. I just meant that folks creating URLs shouldn't use them. I agree that we should try to make them work here if possible.


John H - Mar 25, 2003 2:56:12 pm PST #3605 of 10000

I can fix the URL code if someone can give me a verbal description of what it should do -- and of course show me the current version. I thought it worked by finding http colon slash-slash followed by [any number of characters as long as they're not whitespace] but obviously that's not so or we wouldn't have this problem.

EDIT: by verbal description I mean "it should match http colon slash-slash followed by any character in the following list" or "it should match http colon slash-slash followed by any character not in the following list"


Jon B. - Mar 25, 2003 3:09:10 pm PST #3606 of 10000
A turkey in every toilet -- only in America!

The problem as I understand it is that the URL is delimited by single quotes, so if the URL has an apostrophe, it is read as the end of the URL.


John H - Mar 25, 2003 7:58:41 pm PST #3607 of 10000

The problem as I understand it is that the URL is delimited by single quotes, so if the URL has an apostrophe, it is read as the end of the URL.

That's not it, I'm almost sure.

The website is called something like Martha's Place, and the apostrophe appears in the document name so it's something like "blah.com/martha'splace.html" -- I must say I was really surprised that apostrophes are legal, and it's really not likely to come up very often.

EDIT: ita, can you post the regex that does it? I bet it's a simple fix.