Sorry Jon, you're right, I'm wrong. So the problem could be fixed simply by changing the regex to wrap the URL in double quotes not single. Double quotes are
definitely
not allowed in URLs ... right?
I must admit I'm a bit shocked at the use of single quotes for HTML attribute values. Aren't there some browsers where that would be a big problem?
Double quotes are definitely not allowed in URLs ... right?
I hope not. Better look at the code though, to make sure that won't cause a different problem.
If the regexp is working, we can URLENCODE the URL.
Returns a string in which all non-alphanumeric characters except -_. have been replaced with a percent (%) sign followed by two hex digits and spaces encoded as plus (+) signs
Nothing to add, just joining the throng of the shocked and appalled.
Test 1 2 3
Edit: Sorry, I had a message I thought I posted not show up, and I figured this was a better place to test than elsewhere. Carry on.
Oh! Oh! Oh!
I think I found a solution to the search function overload problems!
We need PIGEONS!
Sorry.
Only if we can poison them in the park...
HTTP/1.1 302 Found
Date: Mon, 31 Mar 2003 14:31:03 GMT
Server: Apache/1.3.27 (Unix) mod_gzip/1.3.26.1a mod_bwlimited/1.0 PHP/4.3.1 mod_log_bytes/1.0 FrontPage/5.0.2.2510 mod_ssl/2.8.12 OpenSSL/0.9.6b
Vary: Accept-Encoding
X-Powered-By: PHP/4.3.1
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Location: Angus G "Buffista Music 1: The Music (And Who Can Blame It) Swells" Mar 31, 2003 2:16:10 am EST
Keep-Alive: timeout=15, max=96
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html
Did we ever find out what cause this sort of error when hitting 'read New" in Safari? After that I get a whole page of HTML.