c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

Public bug reported:

The WebDAV server contains an ugly hack, that installs a pseudo-handler
in the '/' http path, in order to satisfy broken DAV clients. When this
code has originally been written, it used the modular 'static-http.dir_path'
variable. However this had changed in official trunk, thus breaking this
logic.

This breakage, sadly, would extend to more than WebDAV. Since the '/'
contained a badly configured static request handler, this means we would
trigger an unhandled exception for any arbitrary (non-expected) http
request, such as "http://localhost:8069/foo"; . In some cases, with
persistent clients[1], it was observed that the openerp-server process
would keep a thread of http at 100% cpu.

Simply updating the config.options name fixes this.

[1] happens with openerp_libclient, which checks for extra http
protocols.

** Affects: openobject-addons
     Importance: Undecided
     Assignee: xrg (xrg)
         Status: In Progress


** Tags: webdav

** Changed in: openobject-addons
       Status: New => In Progress

** Changed in: openobject-addons
     Assignee: (unassigned) => xrg (xrg)

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/776411

Title:
  webdav: fix config option name, breaking 404 requests

Status in OpenERP Modules (addons):
  In Progress

Bug description:
  The WebDAV server contains an ugly hack, that installs a pseudo-handler
  in the '/' http path, in order to satisfy broken DAV clients. When this
  code has originally been written, it used the modular 'static-http.dir_path'
  variable. However this had changed in official trunk, thus breaking this
  logic.

  This breakage, sadly, would extend to more than WebDAV. Since the '/'
  contained a badly configured static request handler, this means we would
  trigger an unhandled exception for any arbitrary (non-expected) http
  request, such as "http://localhost:8069/foo"; . In some cases, with
  persistent clients[1], it was observed that the openerp-server process
  would keep a thread of http at 100% cpu.

  Simply updating the config.options name fixes this.

  [1] happens with openerp_libclient, which checks for extra http
  protocols.