Errors

Here is my problem, I have apache 1.3.2 on a remote server and on my home windows machine, this ia pretty generic thing though. When I pass information with a space in it to a script, I recieve the error Erroneuous characters after protocol string, I know this can be done because I have seen it, is there some configuration something etc that I can alter to keep this error from occuring? To force it to accept the string? I cannot format the request as a URL properly, and I think there is a way to do it, but I'm not sure how. The script goes something like myfile.php?blah=stuff stuff
I know that after the space it sees the last stuff as protocol so it throws an error, is there any way to keep it from throwing this error or keeping it from occuring?

Try putting the string in quotes

Or change the space into %20

I can't change the spaces, I cannot format the URL at all, it is takes as is. I think that maybe by using a custom error document, I may be able to get it right, but what error number does that return? Quotes don't work either.

How about storing the string in a variable first and then passing the variable?

Ok, lets see if I can make this clearer, I am working on a small script similar to wgat you would see at subprofile.com for AIM. It passes the users screen name to the file. The users screen name can contain spaces, and AIM does not properly encode URLs before pasing them on. So I get
myfile.php?name=my name
not
name=my%20name
or
name=my+name

I have no control over that variable until it hits the server, in which case I can make sure its valid and everything, But the problem is, that it sends an error header back to the AIM client, which gives an error to the user that just says error loading content. I have tried using a custom error document, but I am not 100% sure what the error code for that is. Also, when an error is seen by the server, does it also by default send the error header to the client? If thats the case, is there a way to stop it?

Here's a usenet post from a guy trying to do the same thing...and his solution..not sure if it works, but he says it does:

here

Well that didn;t work at all. Is there a way to stop the error headers from going to the client?