Atlas problem with clean URLs using ISAPI Filter "Isapi_Rewrite"

[Jeeran]

We use an ISAPI filter to convert long urls into short clean ones.
For example:

"Site.com/user/john/"
Is re-written as:
"Site.com/user/userinfo.aspx?uid=john"

Now, "userinfo.aspx" contains a web user control which uses some Atlas functionality;
The web user control contains a "DataList" which gets updated asynchronously
through Atlas when the user clicks a button –the button is the Atlas trigger.

The page acts as it should when we access it using the actual (long) URL,
but when we use the clean url –which goes through the ISAPI filter- we get
a javascript alert through Atlas saying "Unknown Error" when we click the
trigger button.

Any help is greatly appreciated.
Thank you

 

[Laurent Bugnion]

Hi,

We use an ISAPI filter to convert long urls into short clean ones. For
example:
"Site.com/user/john/"
Is re-written as:
"Site.com/user/userinfo.aspx?uid=john"

Now, "userinfo.aspx" contains a web user control which uses some Atlas
functionality; The web user control contains a "DataList" which gets
updated asynchronously through Atlas when the user clicks a button –the
button is the Atlas trigger.

The page acts as it should when we access it using the actual (long)
URL, but when we use the clean url –which goes through the ISAPI filter-
we get a javascript alert through Atlas saying "Unknown Error" when we
click the trigger button.

Any help is greatly appreciated.
Thank you

Normally, and if I am not mistaken, the URL rewriting shouldn't affect
the Atlas call, since the request sent is a normal HTTP request, and
since the redirect is done very early.

If I were you, I would try and use Fiddler to observe the HTTP traffic,
and see exactly what error is sent back from the server.

HTH,
Laurent

 

[Steven Cheng[MSFT]]

Hi Jeeran,

I agree with Laurent, generally speaking, the atlas components should work
transparently to underying IIS ISAPI's url rewriting. If the ISAPI fully
redirect all kinds of requests from faked url to its original url, it shoud
be expected to work. So is your ISAPI filter fully redirecting all kinds of
request( get , post ... ) or with different useragent or headers ?

Also, Jeeran's suggestion on using the Fiddler to trace the http
communication betwwen IE and webserver is a good idea. You can get the
fiddler tool from the following site:

http://www.fiddlertool.com/fiddler/

Please feel free to post here if you have any further findings.

Regards,

Steven Cheng
Microsoft MSDN Online Support Lead


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


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



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

 

[Jeeran]

Hello Steven Cheng[MSFT],

Thank you for the quick response.

We used the Actionless Form described in thie article, and it alls works
fine now. It seems the ISAPI filter handles GET requests by default, and
has to be explicitly told to handle GET requests. I will try that and see
if it works without the actionless form.

The fiddler tool turned out to be very handy, thanks Laurent.

 

[Steven Cheng[MSFT]]

Thanks for your response Jeeran,

Glad that you've made progress on this issue.

Good luck!

Regards,

Steven Cheng
Microsoft MSDN Online Support Lead


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


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



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)