penders - 11:08 am on Mar 19, 2008 (gmt 0)

Are you doing some URL rewriting server side?

<a href='http://example.com/?affid=009090&SID=b3b0172e52dcc6cf61182891904440a3' target=_blank title='strip'>slash</a>

IMHO I would have said that this (with the extra slash) was more correct, since the server is afterall going to have to resolve this to "...com/index.php" (or whatever your default page is)?

<a href='http://example.com&affid=009090&SID=b3b0172e52dcc6cf61182891904440a3' target=_blank title='strip'>slash</a>

I would have said this was invalid. There is no query string marker (?) indicating the end of the URL and the start of the query string. It is just one big URL. And I guess, the server will resolve this as 'http://example.com&affid=009090&SID=b3b0172e52dcc6cf61182891904440a3/index.php'? So a slash at the end is correct.

can anybody help me please to avoid this extra slash and display the actual code generated from the function call?

To change browser behaviour? Hhhmmm, is this possible? If for instance you specify a relative path in your code, the browser will resolve this to an absolute path as you 'hover' over it.

Is the browser breaking your URLs?

---
EDIT: I didn't see that MarkF had already replied :)