1
I’ve been trying for days to figure out why W3’s link validator is charging the following problem:
Lines: 298, 323
http://www.climaxcontoseroticos.com/../perfil_publico.php?autor_perfil=drykaStatus: 400 Bad Request This is usually the Sign of a malformed URL that cannot be Parsed by the server. Check the syntax of the link.
Please explain to me simply. I am new in the area.
Why are you wearing that
/../right there in the url? I believe this is the error he accuses. The right one would be only:http://www.climaxcontoseroticos.com/perfil_publico.php?autor_perfil=dryka– Rafael Withoeft
I don’t think so, the
/../it was the OS that put. if you put the mouse over the link you can see that the url is correct. I clicked on the link here and it was usually, no error– Richard Dias
@Strange richarddias, because I tested the site he posted
/../in W3, and gave the error described. and taking out the/../worked perfectly the validation... See: http://validator.w3.org/check?uri=http%3A%2F%2Fwww.climaxcontoseroticos.com%2Fperfil_publico.php%3Fautor_perfil%3Ddryka&charset=%28detect+Automatically%29&doctype=Inline&group=0– Rafael Withoeft
But you copied the link or clicked on it? By clicking on it it opened normally here
– Richard Dias
@Richarddias I’m talking about the validation of W3, just as he mentioned... both worked normally without the /.. /, but originally with the /.. / he gave error, maybe he pasted wrong the link in W3 too...
– Rafael Withoeft
The site’s link generator changed the link to a valid version. The @bfavaretto edition left the link exactly as it was posted (with the
../)– Gabe
I needed to use the php urlencode() function.
– Peristilo peris