Hi Matt,

you could achieve this by implementing your own RobotMetaTag if you like.
See here for an example:
http://www.gotdotnet.com/Community/...bb-d179927179d5

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"Matt" <anonymous@ilovecms.com> wrote in message
news:21b701c4a155$28c1d420$a601280a@phx.gbl...
> Thanks for your response Stefan, this has helped us fix
> the problem.
>
> I disabled the base tag completely with:
>
> RobotMetaTag1.RenderBaseHref = false;
>
> This had the unfortunate effect of breaking our relative
> references to certain images in our templates. We changed
> these to use absolute URLs and we're back up and running
> with images.
>
> It would be ideal if we could keep the RobotMetaTag web
> control but programatically change the protocol of the URL
> produced in the base tag prior to rendering. I checked the
> API - this doesn't appear to be an available option.

[ Post a follow-up to this message ]