BTreeFolder2: FTP upload not working anymore

Bug #1071431 reported by Georg Pfolz on 2012-10-25
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Undecided
Unassigned

Bug Description

FTP Upload of files into a BTreeFolder2 in the ZODB returns this error:
Server response: '426 Error creating file.'

Hanno Schlichting (hannosch) wrote :

More details would be nice, like a server side traceback. But given how FTP is basically unsupported, this wouldn't surprise me.

Changed in zope2:
status: New → Confirmed
Georg Pfolz (georg-pfolz) wrote :

How do I get the traceback? The event_log and the error_log in the zmi do not show anything, even though I'm in debug-mode.

Georg Pfolz (georg-pfolz) wrote :

I tried again, running Zope in fg-Mode, but there is no error showing up in the console.

Benoît PIN (pinbe) on 2013-06-18
tags: added: webdav
Benoît PIN (pinbe) wrote :

This bug also occurs when you try to put an item thru webdav.

When a PUT request is done (by webdav for instance), the ressource url requested looks like this:
http://my_zope_server.ext/path/to/btreefolder/my_new_file.txt

During traversersing, the object targeted by 'path/to/btreefolder' is correctly retrieved.

Then, the 'my_new_file.txt' is searched, and does not exists, so, a NullResource shoud be created to handle the request.

With a regular folder, it behaves like that.

With the BTreeFolder2, the __getitem__ method, that is used in this case, is inerited from BTreeFolder2.BTreeFolder2Base and does not implement this behavior.

It can be fixed with the patch file joined to be applied at Products/BTreeFolder2/BTreeFolder2.py

Regards,
Benoît.

Benoît PIN (pinbe) wrote :

I've forgotten to mention that the patch also solve the bug for the initial problem reported.

Colin Watson (cjwatson) wrote :

The zope2 project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope2.

Changed in zope2:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers