Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Mar 2021 19:21:46 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 254558] net-mgmt/seafile-server: File-related functionality is broken, always returning 404 when accessing files
Message-ID:  <bug-254558-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254558

            Bug ID: 254558
           Summary: net-mgmt/seafile-server: File-related functionality is
                    broken, always returning 404 when accessing files
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ultima@freebsd.org
          Reporter: ports@stdrand.com
             Flags: maintainer-feedback?(ultima@freebsd.org)
          Assignee: ultima@freebsd.org

(for non-maintainers reading this: see workaround near the bottom)

It would appear that all /seafile links (i.e. any access to a file) result =
in
404 errors.

This happens on all my Seafile instances, and across all tested Seafile
versions:
- 7.1.4 (previous "quarterly")
- 7.1.5 (current "quarterly")
- 8.0.3 (current "latest")

Examples of affected URLs (host & UUIDs omitted for privacy & security
reasons):
- File downloads: https://$HOST/lib/$UUID/file/coy-ast.txt?dl=3D1
- Image downloads: https://$HOST/seafhttp/files/$UUID/browsers.jpg
- Any Seahub functionality that involved opening a file (preview, editing, =
...)

Seahub is completely unaffected, other than functionality that depends on a=
bove
URLs working. For example, login, directory viewing, and library creation a=
ll
work fine --- but I cannot access any of the files.

The issue appears to be centered around the devel/oniguruma dependency (see
below).

OS: FreeBSD 12.2-RELEASE-p3 GENERIC  amd64



WORKAROUND:
I did manage to find the culprit, however: The devel/oniguruma dependency.

oniguruma-6.9.5.r1_1 works fine, but oniguruma-6.9.6 results in this proble=
m.

I've frozen the port version to 6.9.5 for now, but a more permanent fix wou=
ld
be nice.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254558-7788>