Its most likely a problem with the parsing routine in whatever it is you are running. The command line has to be deconstructed by the application (the 'argument pass' where you tell the script/app 'what to do now'). That is usually unique to an application. It could be an un-escaped character, or simply an error. You need to look at the logic in the application. IF its a Unix/Linux born application and not thought through to be cross platform, those kind of errors are common. After a bit of thinking (read below), I'm guessing its an encoding error due to UTF-8(unicode) vs. a Latin ISO set. The function is probably a decodeURI of some type. This could be due to the underlying database setup or the application. This is way out of scope for what we do here, but I was intrigued.
What URL's are possibly permissible under different protocols probably isn't the issue.
this is what to look in, as that is what returned the error -> register.php
this may or may not be the same issue -
Without knowing the applications directory tree its really hard to say what should be happening.
generally, the browser won't be able to access URL's that aren't in the the document root's folder tree without some changes.
not readable by the server.
PHP code isn't an executable, its a script the 'user' needs to have permissions to.
Note that the two errors contain these very close strings - Its possible they are the root of your errors. Whatever you are running, you should probably look at its configuration options. (just a guess) I think the 'parser' routine was looking for an 'austintest1@localhost' (local account)string - pretty sure that's the deal if that is the 'email address' you chose to work with.
that is two different encodings of the '@' and then the unescaped '%' symbol.http://stackoverflow.com/questions/5506 ... l-encodinghttp://www.blooberry.com/indexdot/html/ ... coding.htmhttp://www.coderanch.com/t/527365/socke ... L-encoding
I'm saying you may have two issues - 1st a decoding issue. 2nd. you may also have a folders permissions OR location issue. Solve#1 and maybe #2 goes away - #2 looks like both an encoding issue and a permissions issue.
You need to contact the author.
WORTH READING - ABOUT UTF-8http://www.joelonsoftware.com/articles/Unicode.html