jack13580 - 7:42 am on May 1, 2013 (gmt 0)
I'm going to re explain this
My application parses user in putted urls and determines if they are real or not by if it is returning a 200 header code only, using php and curl
The problem comes when I use a fake url like 1.com for example
My application gets a 200 header code returned even though it doesn't exist
Through research I have determined that my web host might be redirecting that fake url that is being parsed by curl to one of their error pages
Would there be any way to catch this and have it handled by my own custom error page?
Another example of what my web host might be doing is when I enter that fake url myself into my browser and end up getting redirected to a Verizon search page saying that url could not be found