Microsoft Content Management Server - Very strange problem when redirecting from CMS to another app

This is Interesting: Free IT Magazines  
Home > Archive > Microsoft Content Management Server > October 2006 > Very strange problem when redirecting from CMS to another app





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Very strange problem when redirecting from CMS to another app
Andy Stephens

2006-10-19, 1:18 pm

Hi

I don't know if anyone can shed any light on this strange problem.

Our CMS authoring server is also used as our test environment for
run-of-the-mill ASP.Net apps. One of these apps is accessed via a hyperlink
within one of the CMS postings, but once in this app its buttons and
linkbuttons don't work - they fire client-side validators, but if valid input
is supplied they then just reload the current page (no postback occurs). If I
close and reopen the browser and put that very same URL in, the page works
fine.

Similarly (and stranger still), if I bookmark the CMS posting that contains
the hyperlink, and access it this way, then click the hyperlink, the app
again works fine. But if I hit our CMS homepage first, then navigate to the
posting with the hyperlink, this is when the problem occurs.

The only slightly unusual thing that the homepage template is doing is
making use of the CmsHttpContext and WebAuthorContext objects, so I'm
wondering if something is being left "hanging around" within the browser
session that is interfering with the non-CMS app that is accessed later on?

For info (if it's relevant): the CMS app (authoring server, remember) is
using Windows authentication, no impersonation element, and allow users="*".
The problematic ASP.Net app is using Forms authentication. Surely these
wouldn't be clashing with one another would they?

Any suggestions? I'm really stumped with this one.

Thanks in advance,
Andy

Stefan [MSFT]

2006-10-20, 7:19 am

Hi Andy,

sounds more like a browser problem than like a server problem.

Cheers,
Stefan

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


"Andy Stephens" <andrew.stephens@cheshire.gov.uk-donotspam> wrote in message
news:9A7C4E2B-B49A-481A-B41D-277A44B1258F@microsoft.com...
> Hi
>
> I don't know if anyone can shed any light on this strange problem.
>
> Our CMS authoring server is also used as our test environment for
> run-of-the-mill ASP.Net apps. One of these apps is accessed via a
> hyperlink
> within one of the CMS postings, but once in this app its buttons and
> linkbuttons don't work - they fire client-side validators, but if valid
> input
> is supplied they then just reload the current page (no postback occurs).
> If I
> close and reopen the browser and put that very same URL in, the page works
> fine.
>
> Similarly (and stranger still), if I bookmark the CMS posting that
> contains
> the hyperlink, and access it this way, then click the hyperlink, the app
> again works fine. But if I hit our CMS homepage first, then navigate to
> the
> posting with the hyperlink, this is when the problem occurs.
>
> The only slightly unusual thing that the homepage template is doing is
> making use of the CmsHttpContext and WebAuthorContext objects, so I'm
> wondering if something is being left "hanging around" within the browser
> session that is interfering with the non-CMS app that is accessed later
> on?
>
> For info (if it's relevant): the CMS app (authoring server, remember) is
> using Windows authentication, no impersonation element, and allow
> users="*".
> The problematic ASP.Net app is using Forms authentication. Surely these
> wouldn't be clashing with one another would they?
>
> Any suggestions? I'm really stumped with this one.
>
> Thanks in advance,
> Andy
>



Andy Stephens

2006-10-20, 7:19 am

Turns out it was the IIS directory security setting.

Our CMS site is set to Windows integrated, and the other site was just set
to anonymous (which I thought would be okay as it's an internet site open to
all, apart from a folder protected by forms authentication). I had to change
the second site to be both anonymous and windows integrated.

Thanks anyway.


"Stefan [MSFT]" wrote:

> Hi Andy,
>
> sounds more like a browser problem than like a server problem.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
>
> "Andy Stephens" <andrew.stephens@cheshire.gov.uk-donotspam> wrote in message
> news:9A7C4E2B-B49A-481A-B41D-277A44B1258F@microsoft.com...
>
>
>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com