Re: 409 status code response from WebDAV appointment msg
- From: "Darren From OZ" <DarrenFromOZ@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 26 Oct 2005 15:57:04 -0700
Hi Lee, Thanks for the response.
We are POSTing to a particular users calendar subfolder with the intention
of creating a new entry, like:
http://adas0133a/Exchange/dguilber/Calendar/dgappoint.eml
We are trying to work out a way to use Method=PROPPATCH from our java
technology stack - but we are a little limitted as the API we have to use
only supports HTTP POST and GET.
Thanks.
"Lee Derbyshire [MVP]" wrote:
> "Darren From OZ" <Darren From OZ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:E6A9B857-0508-4DFC-A0AB-F85DCF9BB834@xxxxxxxxxxxxxxxx
> > Hi,
> > We are using java and trying to POST a WebDAV message to an Exchange
> 2003
> > server in order to create a new Calendar entry. I believe we have
> > authentication working OK (no longer getting 401's), But now IIS
> 6/Exchange
> > 2003 is replying to the message with a HTTP status code = 409 (no
> subcodes
> > mentioned in the log).
> > The exchange help notes this as a "resource conflict" error -
> possibly
> > meaning that some of the contents of the message are incorrect.
> >
> > We have the WebDAV extensions on IIS 6 enabled.
> >
> > Following is the message we are using to create the new calendar
> entry. Any
> > ideas what is wrong with this message ? Also, Should a HTTP method =
> POST
> > work for sending this message, or is a Method=PROPPATCH strictly
> required.
> > Many thanks. Darren.
> >
> > <g:propertyupdate xmlns:g="DAV:"
> > xmlns:e="http://schemas.microsoft.com/exchange/"
> > xmlns:mapi="http://schemas.microsoft.com/mapi/proptag/"
> xmlns:x="xml:"
> > xmlns:cal="urn:schemas:calendar:"
> > xmlns:dt="urn:uuid:c2f41010-65b3-11d1-a29f-00aa00c14882/"
> > xmlns:header="urn:schemas:mailheader:"
> xmlns:mail="urn:schemas:httpmail:">
> > <g:set>
> > <g:prop>
> > <g:contentclass>urn:content-classes:appointment</g:contentclass>
> > <e:outlookmessageclass>IPM.Appointment</e:outlookmessageclass>
> > <mail:subject>meetappt Subject</mail:subject>
> > <mail:htmldescription>Let's meet here</mail:htmldescription>
> > <cal:location>meetappt Location</cal:location>
> > <cal:dtstart
> dt:dt="dateTime.tz">2005-10-261T10:00:00.000Z</cal:dtstart>
> > <cal:dtend dt:dt="dateTime.tz">2005-10-26T12:00:00.000Z</cal:dtend>
> > <cal:instancetype dt:dt="int">0</cal:instancetype>
> > <cal:meetingstatus>CONFIRMED</cal:meetingstatus>
> > <cal:alldayevent dt:dt="boolean">0</cal:alldayevent>
> > <cal:responserequested dt:dt="boolean">1</cal:responserequested>
> > <cal:uid>123456789</cal:uid>
> > <header:to>HCM1@xxxxxxxxxxxxxxxxxxxxxxxxx</header:to>
> > <header:cc>HCM1@xxxxxxxxxxxxxxxxxxxxxxxxx</header:cc>
> > <header:bcc>HCM1@xxxxxxxxxxxxxxxxxxxxxxxxx</header:bcc>
> > <mapi:finvited dt:dt="boolean">1</mapi:finvited>
> > <mapi:responsestatus dt:dt="int">1</mapi:responsestatus>
> > <mapi:responsestate dt:dt="int">0</mapi:responsestate>
> > <mapi:response_requested dt:dt="boolean">1</mapi:response_requested>
> > <mapi:apptstateflags dt:dt="int">3</mapi:apptstateflags>
> > <mapi:busystatus dt:dt="int">1</mapi:busystatus>
> > <mapi:intendedbusystatus dt:dt="int">2</mapi:intendedbusystatus>
> > </g:prop>
> > </g:set>
> > </g:propertyupdate>
>
> The 409 Resource Conflicts are a pain, and sometimes very hard to
> solve. What URL are you posting to? Are you posting to the folder
> URL, or providing a complete unique new message URL?
>
> Actually, I think I would use PROPPATCH for this, too, instead of
> POST.
>
> Lee.
>
> --
> _______________________________________
>
> Outlook Web Access For PDA , OWA For WAP
> www.owapda.com
> email a@t leederbyshire d.0.t c.0.m
> _______________________________________
>
>
>
.
- Follow-Ups:
- Re: 409 status code response from WebDAV appointment msg
- From: Lee Derbyshire [MVP]
- Re: 409 status code response from WebDAV appointment msg
- References:
- Re: 409 status code response from WebDAV appointment msg
- From: Lee Derbyshire [MVP]
- Re: 409 status code response from WebDAV appointment msg
- Prev by Date: Re: Unique ID for Exchange
- Next by Date: Re: setting message item sent status...
- Previous by thread: Re: 409 status code response from WebDAV appointment msg
- Next by thread: Re: 409 status code response from WebDAV appointment msg
- Index(es):
Relevant Pages
|