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

Need incremental iCalendar parsing to avoid blocking #411

Closed
macosforgebot opened this issue Aug 29, 2006 · 9 comments
Closed

Need incremental iCalendar parsing to avoid blocking #411

macosforgebot opened this issue Aug 29, 2006 · 9 comments

Comments

@macosforgebot
Copy link

@macosforgebot macosforgebot commented Aug 29, 2006

@dreid originally submitted this as ticket:40


http_PUT blocks while storing the calendar data, and it can take up to 5 minutes for a request involving a 208K ics file to complete. This is obviously a pretty good place for a DoS to happen. I suspect the culprit is the calendar validation, this stuff should be deferred to a thread.

Note we have a similar problem with XML; we probably need to switch to ElementTree or similar.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Sep 7, 2006

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

  • Status changed from new to assigned
  • Priority changed from 1: Blocker to 2: Expected
  • Severity changed from Serious to Performance
  • Milestone set to Preview 1

Ew, yes.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Sep 12, 2006

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

  • Description modified

We're going to need an iCalendar parser that can do incremental parsing, which means adding that capability to vobject. Not sure how much work that's going to be...

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Sep 12, 2006

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

  • Summary changed from http_PUT blocks to Need incremental iCalendar parsing to avoid blocking

See #⁠16

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Jan 29, 2007

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

  • Milestone changed from Preview 1 to Version One
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Jul 30, 2007

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

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

@macosforgebot macosforgebot commented Oct 26, 2009

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

  • Milestone changed from CalendarServer-2.x to CalendarServer-3.x
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Oct 26, 2009

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

  • Owner changed from @wsanchez to @glyph
  • Status changed from assigned to new
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Aug 1, 2011

@wsanchez originally submitted this as comment:8:⁠ticket:40

  • Radar deleted
  • Milestone changed from CalendarServer-3.x to Later
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Mar 26, 2015

@wsanchez originally submitted this as comment:14:⁠ticket:40

  • Status changed from new to closed
  • Resolution set to Not to be fixed

Expiring old bugs with unknown state and impact.

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
1 participant
You can’t perform that action at this time.