Home All Groups Group Topic Archive Search About

Exchange 2007 appointment creation using a POST request return HTTP 403 (forbiden)

Author
28 Sep 2007 3:09 PM
Dom
The used request works fine on Exchange 2000 and Exchange 2003, but
there is no way to make it works on Exchange 2007, always the same
answer: HTTP 403.

I don't think it's an authentication problem, because all the other
requests work fine (PROPPATCH, PROPFIND, ...) with the same Basic
Authentication.

The Exchange 2007 server "seems" to be configured like my Exchange
2003 server.
(maybe i'm missing something ?)

Does anyone have an idea please ?

Here is the request (ethereal trace):

POST /exchange/testdom/Calendrier HTTP/1.1
Content-Type: application/x-www-UTF8-encoded
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET
CLR 1.1.4322)
Host: 192.168.10.155
Content-Length: 495
Connection: Keep-Alive
Cache-Control: no-cache
Pragma: no-cache
Cookie:
UserContext_9429d2e8ecd140dd887381409e309567=4bc77d4204a8425faefa1e9b46de1c27&c210cDp0ZXN0ZG9tQGFsZXhjaDIwMDcuYWw2NC5jb20
Authorization: Basic
YWxleGNoMjAwNy5hbDY0LmNvbVx0ZXN0ZG9tOkFyYXZpczEyMw==

Cmd=saveappt
Required=
Optional=
Resource=
FormType=appointment
DAV:contentclass=urn:content-classes:appointment
urn:schemas:httpmail:subject=Appointment subject
http://schemas.microsoft.com/exchange/subject-utf8=Appointment subject
urn:schemas:calendar:dtstart=2008-06-04T15:00:00.000Z
urn:schemas:calendar:dtend=2008-06-04T16:00:00.000Z
urn:schemas:calendar:location=We'll meet here!
urn:schemas:calendar:alldayevent=0
urn:schemas:calendar:busystatus=FREE
urn:schemas:httpmail:textdescription=

And the response:
HTTP/1.1 403 Interdit
Connection: close
Date: Thu, 27 Sep 2007 07:39:13 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/html
Content-Length: 140
MS-WebStorage: 08.00.10685
Cache-Control: no-cache

<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
</HEAD>
<body><h2>HTTP/1.1 403 Interdit</h2></body></HTML>

Thank you for your help.

Author
28 Sep 2007 3:59 PM
Henning Krause [MVP - Exchange]
Hello,

Exchange 2007 uses SSL by default. So instead htp://server/... use
https://server/...

Kind regards,
Henning Krause

Loim
Show quote
"Dom" <dominique.foueillas***@gmail.com> wrote in message
news:1190992142.722550.220530@50g2000hsm.googlegroups.com...
> The used request works fine on Exchange 2000 and Exchange 2003, but
> there is no way to make it works on Exchange 2007, always the same
> answer: HTTP 403.
>
> I don't think it's an authentication problem, because all the other
> requests work fine (PROPPATCH, PROPFIND, ...) with the same Basic
> Authentication.
>
> The Exchange 2007 server "seems" to be configured like my Exchange
> 2003 server.
> (maybe i'm missing something ?)
>
> Does anyone have an idea please ?
>
> Here is the request (ethereal trace):
>
> POST /exchange/testdom/Calendrier HTTP/1.1
> Content-Type: application/x-www-UTF8-encoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET
> CLR 1.1.4322)
> Host: 192.168.10.155
> Content-Length: 495
> Connection: Keep-Alive
> Cache-Control: no-cache
> Pragma: no-cache
> Cookie:
> UserContext_9429d2e8ecd140dd887381409e309567=4bc77d4204a8425faefa1e9b46de1c27&c210cDp0ZXN0ZG9tQGFsZXhjaDIwMDcuYWw2NC5jb20
> Authorization: Basic
> YWxleGNoMjAwNy5hbDY0LmNvbVx0ZXN0ZG9tOkFyYXZpczEyMw==
>
> Cmd=saveappt
> Required=
> Optional=
> Resource=
> FormType=appointment
> DAV:contentclass=urn:content-classes:appointment
> urn:schemas:httpmail:subject=Appointment subject
> http://schemas.microsoft.com/exchange/subject-utf8=Appointment subject
> urn:schemas:calendar:dtstart=2008-06-04T15:00:00.000Z
> urn:schemas:calendar:dtend=2008-06-04T16:00:00.000Z
> urn:schemas:calendar:location=We'll meet here!
> urn:schemas:calendar:alldayevent=0
> urn:schemas:calendar:busystatus=FREE
> urn:schemas:httpmail:textdescription=
>
> And the response:
> HTTP/1.1 403 Interdit
> Connection: close
> Date: Thu, 27 Sep 2007 07:39:13 GMT
> Server: Microsoft-IIS/6.0
> X-Powered-By: ASP.NET
> Content-Type: text/html
> Content-Length: 140
> MS-WebStorage: 08.00.10685
> Cache-Control: no-cache
>
> <HTML>
> <HEAD>
> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
> </HEAD>
> <body><h2>HTTP/1.1 403 Interdit</h2></body></HTML>
>
> Thank you for your help.
>
Author
28 Sep 2007 6:46 PM
Lee Derbyshire [MVP]
Show quote
"Dom" <dominique.foueillas***@gmail.com> wrote in message
news:1190992142.722550.220530@50g2000hsm.googlegroups.com...
> The used request works fine on Exchange 2000 and Exchange 2003, but
> there is no way to make it works on Exchange 2007, always the same
> answer: HTTP 403.
>
> I don't think it's an authentication problem, because all the other
> requests work fine (PROPPATCH, PROPFIND, ...) with the same Basic
> Authentication.
>
> The Exchange 2007 server "seems" to be configured like my Exchange
> 2003 server.
> (maybe i'm missing something ?)
>
> Does anyone have an idea please ?
>
> Here is the request (ethereal trace):
>
> POST /exchange/testdom/Calendrier HTTP/1.1
> Content-Type: application/x-www-UTF8-encoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET
> CLR 1.1.4322)
> Host: 192.168.10.155
> Content-Length: 495
> Connection: Keep-Alive
> Cache-Control: no-cache
> Pragma: no-cache
> Cookie:
> UserContext_9429d2e8ecd140dd887381409e309567=4bc77d4204a8425faefa1e9b46de1c27&c210cDp0ZXN0ZG9tQGFsZXhjaDIwMDcuYWw2NC5jb20
> Authorization: Basic
> YWxleGNoMjAwNy5hbDY0LmNvbVx0ZXN0ZG9tOkFyYXZpczEyMw==
>
> Cmd=saveappt
> Required=
> Optional=
> Resource=
> FormType=appointment
> DAV:contentclass=urn:content-classes:appointment
> urn:schemas:httpmail:subject=Appointment subject
> http://schemas.microsoft.com/exchange/subject-utf8=Appointment subject
> urn:schemas:calendar:dtstart=2008-06-04T15:00:00.000Z
> urn:schemas:calendar:dtend=2008-06-04T16:00:00.000Z
> urn:schemas:calendar:location=We'll meet here!
> urn:schemas:calendar:alldayevent=0
> urn:schemas:calendar:busystatus=FREE
> urn:schemas:httpmail:textdescription=
>
> And the response:
> HTTP/1.1 403 Interdit
> Connection: close
> Date: Thu, 27 Sep 2007 07:39:13 GMT
> Server: Microsoft-IIS/6.0
> X-Powered-By: ASP.NET
> Content-Type: text/html
> Content-Length: 140
> MS-WebStorage: 08.00.10685
> Cache-Control: no-cache
>
> <HTML>
> <HEAD>
> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
> </HEAD>
> <body><h2>HTTP/1.1 403 Interdit</h2></body></HTML>
>
> Thank you for your help.

As a side note, I would recommend you change your logon password, since you
have posted your Base64 encoded credentials.

Lee.

--
_______________________________________

Outlook Web Access for PDA, OWA For WAP:
www.leederbyshire.com
________________________________________
Author
1 Oct 2007 10:00 AM
Dom
Hello,

> As a side note, I would recommend you change your logon password, since you
> have posted your Base64 encoded credentials.
Thank you for your suggestion, but the server is on a private network,
there is no problems, thanks.

> Exchange 2007 uses SSL by default. So instead htp://server/... use
> https://server/...
I configured Exchange 2007 to use http, and not https (using https is
another story, with others problems...:-) )

As i said before:
"all the others requests work fine (PROPPATCH, PROPFIND, ...) with the
same Basic Authentication..."
some examples:

I can read the Tasks:
SEARCH on http://192.168.10.155/exchange/testdom/T%C3%A2ches ==> 207
(ok)

I can write the Tasks:
PROPPATCH on http://192.168.10.155/exchange/testdom/T%C3%A2ches/%7B000003b8-4700bca1-00000003%7D_20071001_4.EML
==> 207 (ok)

I can read the Calendar:
SEARCH        on http://192.168.10.155/exchange/testdom/Calendrier ==>
207 (ok)

but.... i can't write the Calendar:
POST             on http://192.168.10.155/exchange/testdom/Calendrier
==> 403 (ko !!!)

Is there something wrong in the content of the POST, that would be
right for Exchange 2000 and Exchange 2003, but wrong for Exchange
2007 ?:
==============================================
Cmd=saveappt
Required=
Optional=
Resource=
FormType=appointment
DAV:contentclass=urn:content-classes:appointment
urn:schemas:httpmail:subject=Appointment subject
http://schemas.microsoft.com/exchange/subject-utf8=Appointment subject
urn:schemas:calendar:dtstart=2008-06-04T15:00:00.000Z
urn:schemas:calendar:dtend=2008-06-04T16:00:00.000Z
urn:schemas:calendar:location=We'll meet here!
urn:schemas:calendar:alldayevent=0
urn:schemas:calendar:busystatus=FREE
urn:schemas:httpmail:textdescription=
==============================================

Is there something special with the POST method in Exchange 2007 ?
(different from Exchange 2000 and Exchange 2003)

Thanks for your response...

Dom.
Author
1 Oct 2007 1:19 PM
Dom
More information about that:

I used the code given at this page:
http://msdn2.microsoft.com/en-us/library/ms877306.aspx

to create an appointment with PROPPATCH method on Exchange 2007, and
it works !!!!!
it works too on Exchange 2000.


My question is: what's happen with POST method in Exchange 2007 to
create appointments ? (a large part of our application is using
it.......)


Thanks,

Dom.
Author
1 Oct 2007 2:14 PM
Lee Derbyshire [MVP]
Show quote
"Dom" <dominique.foueillas***@gmail.com> wrote in message
news:1191244770.916715.219920@r29g2000hsg.googlegroups.com...
> More information about that:
>
> I used the code given at this page:
> http://msdn2.microsoft.com/en-us/library/ms877306.aspx
>
> to create an appointment with PROPPATCH method on Exchange 2007, and
> it works !!!!!
> it works too on Exchange 2000.
>
>
> My question is: what's happen with POST method in Exchange 2007 to
> create appointments ? (a large part of our application is using
> it.......)
>
>
> Thanks,
>
> Dom.

The OWA 2007 GUI has changed too much. These workarounds (pretending to be
OWA and using POST to simulate a form submission) no longer work because it
doesn't recognize what you are posting.  Also, most non-WebDAV verbs seem to
be blocked from the /Exchange directory now.

Lee.

--
______________________________________

Outlook Web Access For PDA , OWA For WAP
www.leederbyshire.com
email a@t leederbyshire d.0.t c.0.m
______________________________________
Author
1 Oct 2007 3:13 PM
Dom
Hello Lee,

Thanks for your response, but if you're right, we have a big
problem :-|

Does anyone can confirm that the /Exchange directory of Exchange 2007
version does not support anymore non-WebDAV verbs, like POST ???


Dom.
Author
2 Oct 2007 1:05 PM
GvO
I checked the server capabilities for my exchange 2007 mailbox with the
program Mistaya. Connect to your mailbox -> right click on your mailbox ->
Capabilities. Then you get a window with the allowed methods. In my case it's
not allowed any more. Sorry :-(

Guido


Show quote
"Dom" wrote:

> Hello Lee,
>
> Thanks for your response, but if you're right, we have a big
> problem :-|
>
> Does anyone can confirm that the /Exchange directory of Exchange 2007
> version does not support anymore non-WebDAV verbs, like POST ???
>
>
> Dom.
>
>
Author
2 Oct 2007 2:58 PM
Dom
Hello Guido, thanks for your response,

You're right, when we ask for capabilities on Exchange 2007 we've got
this response:
<Public>OPTIONS, TRACE, GET, HEAD, DELETE, PUT, POST, COPY, MOVE,
MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, SEARCH, SUBSCRIBE,
UNSUBSCRIBE, POLL, BDELETE, BCOPY, BMOVE, BPROPPATCH, BPROPFIND</
Public>
  <Allow>OPTIONS, TRACE, GET, HEAD, DELETE, COPY, MOVE, PROPFIND,
PROPPATCH, SEARCH, SUBSCRIBE, UNSUBSCRIBE, POLL, BDELETE, BCOPY,
BMOVE, BPROPPATCH, BPROPFIND, MKCOL, LOCK, UNLOCK</Allow>

We can notice that the POST verb is on the 'Public' list, but not on
the 'Allow' list.


But.... when we ask for capabilities on Exchange 2000 for example,
we've got the same answer !!!! ==> POST is on the 'Public' list, and
IS NOT on the 'Allow' list.
Nevertheless, on Exchange 2000, i can create an appointment item using
a POST request......

There is something more....

Dom.
Author
2 Oct 2007 3:19 PM
Lee Derbyshire [MVP]
I think it works in previous versions of Exchange because the /Exchange URL
was used for both OWA access and WebDAV access.  If you sent a verb that a
browser might send (such as GET or POST), it behaved like OWA.  If you send
a DAV verb (PROPFIND, etc), then it knew you were using DAV.  However, there
are lots and lots of things you just can't do with DAV, so people learned to
simulate an OWA action to get certain jobs done.

Now that E2007 uses the /OWA URL for OWA, those tricks doesn't appear to
work any more.

Lee.

--
______________________________________

Outlook Web Access For PDA , OWA For WAP
www.leederbyshire.com
email a@t leederbyshire d.0.t c.0.m
______________________________________

Show quote
"Dom" <dominique.foueillas***@gmail.com> wrote in message
news:1191337127.527867.84580@50g2000hsm.googlegroups.com...
> Hello Guido, thanks for your response,
>
> You're right, when we ask for capabilities on Exchange 2007 we've got
> this response:
> <Public>OPTIONS, TRACE, GET, HEAD, DELETE, PUT, POST, COPY, MOVE,
> MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, SEARCH, SUBSCRIBE,
> UNSUBSCRIBE, POLL, BDELETE, BCOPY, BMOVE, BPROPPATCH, BPROPFIND</
> Public>
>  <Allow>OPTIONS, TRACE, GET, HEAD, DELETE, COPY, MOVE, PROPFIND,
> PROPPATCH, SEARCH, SUBSCRIBE, UNSUBSCRIBE, POLL, BDELETE, BCOPY,
> BMOVE, BPROPPATCH, BPROPFIND, MKCOL, LOCK, UNLOCK</Allow>
>
> We can notice that the POST verb is on the 'Public' list, but not on
> the 'Allow' list.
>
>
> But.... when we ask for capabilities on Exchange 2000 for example,
> we've got the same answer !!!! ==> POST is on the 'Public' list, and
> IS NOT on the 'Allow' list.
> Nevertheless, on Exchange 2000, i can create an appointment item using
> a POST request......
>
> There is something more....
>
> Dom.
>

AddThis Social Bookmark Button