http://www.antionline.com/showthread...903#post779887
The URL keeps screwing up. I pasted it correctly several times.
Printable View
http://www.antionline.com/showthread...903#post779887
The URL keeps screwing up. I pasted it correctly several times.
Works fine for me when i click on the link in your post :)
Sir Dice, see this thread. I'm wondering if it's specific to browser issue. I've run into the problem on my slack with Mozilla. fyrewall, what browser are you using?
I'm currently using IE6.0. Funny thing is, my URL looks ok in the statusbar (yours doesn't btw). It only screws up when I click on it.
Edit: Correction...Both (mine and yours) are fscked in the statusbar.
im using firefox 0.9.3 on win2k3 server :)
Odd. Why would it work with firefox?
The URL is screwed up in the source of the page.
Source looks like this on my end:
Code:<br />
Here's some explaination, it's for another type of equipment but the connections are the same.<br />
<br />
<a href="http://cisco.com/en/US/products/hw/switches/ps605/ products_installation_guide_chapter09186a008007eac<br />
0.html" target="_blank">Connectors and Cable Specifications</a><br />
<br />
Could firefox be ignoring the space?
I thought you meant the link to the thread wasnt working not the cisco link .. sorry dude :) lol
my bad
/me feels stupid :(
the cisco link doesnt work for me
Ok. So it doesn't work in firefox. Sir Dice, we need to wait for mnstrgrl to return from where ever she's been hanging out at and see if she can find the problem and fix it. :)
Alright. No problem. You can merge this thread with yours if you want (to keep things nice and tidy ;) )
Is it possible that there was a line break in the middle of the URL when you pasted it into your reply? Line breaks are changed to break tags when a reply is submitted.
If that's not it, the only other thing I can imagine is that the post text got wrapped, and the URL was long enough that it was cut up in the wrapping. Here's my test:
http://cisco.com/en/US/products/hw/s...08007eac0.html
Edit It's being wrapped by the thread display code... looking into that now.
- h