Exchange Server

Jon Hewitt · Guest

Hi,

I'm using the Free/Busy HTTP Command to fetch Free/Busy time as described by
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/_esdk_checking_free_busy_status_http.asp
successfully against an Exchange 2003 server. Unfortunately when I try to do
the same thing against an Exchange 2000 server, I get the wrong content. I
am trying to get the XML content which is associated with the IE browser but
instead I always get the HTML content designated for non-IE browsers. I even
get the non-IE content when I use IE to send the request. An example URL I
am using is:

http://<exchangeserver>/public/?cmd=freebusy&start=2005-08-27T08:00:00Z&end=2005-08-27T20:00:00Z&interval=60&u=SMTP:<mail-address>

Any advice on how to address this problem?

- Jon

Glen Scales [MVP] · Guest

Try adding a header for User-Agent this will make sure that Exchange knows
your using IE 5.0 or higher eg

request.setRequestHeader "User-Agent", "Mozilla/4.0 (compatible; MSIE 6.0;
Windows NT 5.1; SV1; .NET CLR 1.1.4322)"

Cheers
Glen

"Jon Hewitt" <Jon Hewitt@discussions.microsoft.com> wrote in message
news:5A76DBD5-6066-4980-A57A-7FA627335088@microsoft.com...

Jon Hewitt · Guest

I agree that setting the User-Agent would seem to be the proper approach but
the results I am seeing suggest something else may be in play.

1) When you request the page from IE 6, Exchange 2000 still doesn't send the
IE content.
2) I can send a User Agent of "Mozilla/4.0 (Compatible; MSIE 6.0; Windows NT
5.0)" to our Exchange 2003 and I get the correct results. Sending the same
header to Exchange 2000 gives the incorrect results.
3) I have also tried other User Agents like "Mozilla/4.0 (compatible; MSIE
5.0; Windows NT 5.0)" and still no luck.

- Jon

"Glen Scales [MVP]" wrote:

Glen Scales [MVP] · Guest

This work fine for me on a Exchange 2000 server you might want to take a
closer look at IIS maybe the way URLscan has been configured could be
affecting the query. Also doing a packet capture of the request using
something like ethereal might help give you more information about what's
happening. Are you trying this from a workstation or directly on the server.
What happens if you try this from the browser locally on the server does
this make a difference. Are there any proxies or firewalls (include locally
PC firewalls) between the server and client. Check the IIS logs on the
server this should tell you if the query is making it intact to the server

Cheers
Glen

"Jon Hewitt" <JonHewitt@discussions.microsoft.com> wrote in message
news:6335DD0F-BFBC-4AA6-ACFC-BAF0481DADA9@microsoft.com...

Jon Hewitt · Guest

I get the same results using IE on the Exchange server. The Exchange logs
show that the URL is getting through correctly.

Also it appears that all of OWA screens render as non-IE content.

So it seems there must be some misconfiguration but the logs I have seen
don't give any good direction on what that might be.

- Jon

"Glen Scales [MVP]" wrote:

Jon Hewitt · Guest

Solution! The Exchange server had the ForceClientsDownLevel registry setting
turned on for OWA. Removing it gave me the expected results.

Thanks Glen for the help!

	Exchange Server Forum Index -> Development	All times are GMT
Page 1 of 1