Skip to content
This repository has been archived by the owner. It is now read-only.

Calendar Server should verify that addresses are valid #125

Closed
macosforgebot opened this issue Apr 19, 2007 · 7 comments
Closed

Calendar Server should verify that addresses are valid #125

macosforgebot opened this issue Apr 19, 2007 · 7 comments

Comments

@macosforgebot
Copy link

@macosforgebot macosforgebot commented Apr 19, 2007

@wsanchez originally submitted this as ticket:150


3/27/07 3:21 PM Wilfredo Sanchez: Calendar Server should verify that addresses are valid

Where possible, the server should verify the validity of URI forms used as calendar user addresses. Right now, if your client sends us a CUA of "mailto:Joe" the server happily stores it. Since this could cause another client to raise an error, this should be caught and prohibited by the server.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Apr 19, 2007

@wsanchez originally submitted this as comment:1:⁠ticket:150


3/27/07 3:22 PM Wilfredo Sanchez: Perhaps in iComponent.validateForCalDAV() or some such

3/28/07 6:56 AM Cyrus Daboo: Given that every URI scheme has its own syntax, it would be a little hard to validate all of them. Certainly we could do the common ones we expect to deal with, mailto, http, https, ldap, urb:uuid.

We would have to ensure this is checked on a regular PUT, a COPY or MOVE into a calendar collection (from a non-calendar collection at least), and for POST on Outbox.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Apr 19, 2007

@wsanchez originally submitted this as comment:2:⁠ticket:150


Yeah, I'm satisfied if we simply catch what we can. At least it'll avoid some interop problems.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Jul 30, 2007

@wsanchez originally submitted this as comment:3:⁠ticket:150

  • Milestone changed from 1.0 to 1.1
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Dec 15, 2007

@wsanchez originally submitted this as comment:4:⁠ticket:150

  • Milestone changed from 1.1 to 1.2
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Jan 23, 2008

@wsanchez originally submitted this as comment:5:⁠ticket:150

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Oct 28, 2008

@wsanchez originally submitted this as comment:6:⁠ticket:150

  • Milestone changed from CalendarServer-1.x to CalendarServer-2.0
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Mar 9, 2009

@wsanchez originally submitted this as comment:7:⁠ticket:150

  • Status changed from new to closed
  • Resolution changed from to Software changed

Bogus mailto: now results in an error if server-side mail sending is enabled.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.