-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CalDAV. What to do with MKCALENDAR request? #109
Comments
One of possible workarounds is to setup a frontend server (like Nginx or else) and rewrite this method to some other (POST maybe?) and add special header (X-Original-Method: MKCALENDAR) then on NodeJS side rewrite it back before passing to DAV server |
Another possible workaround is to implement some HTTP-server with node-parsely (https://github.com/substack/node-parsley) and create some custom objects implementing request/response public API, when pass them to DAV server |
Apparently it all boils down to nodejs/node-v0.x-archive#3192 -> nodejs/http-parser#158 Did you try the method in last message of this thread https://groups.google.com/forum/#!msg/nodejs/0KDuxleCoxE/oVDCzka_4nYJ, may be the random dropping behaviour was solved in latest nodes. |
@aenario no, I'm not. Just discovered this issue last night. Still discovering. I think I will use front-end method in my case (I'm already have Nginx instance in front of my CalDAV server) |
In CalDAV, new calendar is made via non-standard HTTP request MKCALENDAR.
Current version of NodeJS have no support for non-standard custom methods like this one (https://groups.google.com/forum/#!msg/nodejs/0KDuxleCoxE/oVDCzka_4nYJ).
What workaround can be recommended for this?
The text was updated successfully, but these errors were encountered: