URL Routing and Relative Links Behavior

I'm building a website that stores a number of articles. The URL for each articles implements URL routing in the form /Articles/{categoryid}/{articleslug}.

Some articles have links to a graphics file. The link does not specify the full path so I'm storing the graphics file at /Articles/{开发者_JS百科categoryid}/{articleslug}/graphic.jpg.

This works fine on my desktop. But when I deployed the site to a shared hosting account, the behavior is different.

Now, the link only works if I store the graphics file at /Articles/{categoryid}/graphic.jpg. In other words, on my desktop, the {articleslug} is assumed to be a directory, but on the web it is assumed to be the name of the current page.

Does anyone know why the behavior changes? You can seen an example at http://www.blackbeltcoder.com/Articles/asp/creating-website-thumbnails-in-asp-net. Both the screenshot and download link near the top are broken links.

Without knowing more, it seems like the most likely cause would be a different version or configuration of IIS. The behavior of the web host makes all kinds of sense; the behavior of your desktop is confusing to me. Is your desktop doing a redirect from /Articles/{categoryid}/{articleslug} to /Articles/{categoryid}/{articleslug}/? Can you use Fiddler etc to see if the browser formats the GET request differently?

Thanks for the input. There probably wasn't enough information here for anyone to resolve this unless they've specifically seen the issue already.

At any rate, I was able to resolve it myself and I describe the resolution in a related question I posted at Relative Links with Extension-less URLs.

Thanks.