Skip to content
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

OC10: regression with custom sharing provider #27617

Closed
labkode opened this issue Apr 11, 2017 · 8 comments
Closed

OC10: regression with custom sharing provider #27617

labkode opened this issue Apr 11, 2017 · 8 comments
Assignees

Comments

@labkode
Copy link

labkode commented Apr 11, 2017

When using our custom sharing manager factory:

'sharing.managerFactory' => 'OC\\CernBox\\Share\\ProviderFactory',

ownCloud returns 500 error with following log line message:

{"reqId":"WOyOsv@Wx9-EDjb9ySZFSgAAAAo","remoteAddr":"128.141.150.68","app":"no app in context","message":"CSRF check failed","level":0,"time":"2017-04-11T08:07:14+00:00","method":"GET","url":"\/index.php\/apps\/files_sharing\/api\/externalShares","user":"gonzalhu"}
@PVince81
Copy link
Contributor

CSRF check failed? Sometimes that message happens due to infinite recursions.

Can you debug the the code and provide more info ? So far that's not enough info to be able to provide help.

@PVince81
Copy link
Contributor

another option is bisecting to find out what commit broke it

@PVince81
Copy link
Contributor

closing, not enough info.

@labkode
Copy link
Author

labkode commented Apr 21, 2017

Hello,

we don't have time now for debugging these kind of regressions.

Please leave the issue open so we do not forget about it.

@moscicki
Copy link

@PVince81: how do you actually test "pluggability" with your interfaces such as sharing.managerFactory? You must surely have a simple mockup class for testing which proves that something else than a default, legacy implementation can be plugged in?

We have seen before (#26607) that your system is not properly separated into independent components and you have implicit dependencies which violate the interfaces.

@PVince81
Copy link
Contributor

As far as I know there are currently no proper tests for pluggability.

Ideal would probably be to have a test instance with a custom sharing manager / storage implementations that runs in a separate test suite.

Most of the refactored Sharing v2 components should already be decoupled as much as possible. The remaining code that was discovered is from Sharing v1 and is mostly unused. Needs clean up.

Note that Sharing and FS need to be implemented together, these two components cannot be separated. This means that the current sharing code can use filecache and if someone reimplements the filecache logic they also need to reimplement that matching sharing part.

@DeepDiver1975

@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label needs info is set and there were no updates for 14 days. Feel free to reopen this issue if you deem it appropriate.

@lock
Copy link

lock bot commented Aug 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants