Tag Info

New answers tagged

1

Your content is going into an HTML attribute, encoded in a URL. That gives you two possible forms of encoding: URL-encoding: %2F. Although this should in principle work, both IIS and Apache block the use of URL-encoded slashes due to some past security issues. HTML-encoding: /, or rather as it is itself in a URL, %26%2347%3B. (Although... since ...


0

Remove the whole %20path=/ section - the HTTP response header should set everything at root level. If that doesn't work inside a meta http-eqiv, try the HTML encoded version of the path as because the content is in HTML should be correctly decoded (/). Alternatively you could inject JavaScript to set the cookie via client-side script and set the ...


0

Try URL encoding the / character with the hex representation %2F.



Top 50 recent answers are included