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.

Sign up for GitHub

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

Jump to bottom

/content endpoint #806

Merged
merged 6 commits into from
Aug 11, 2022
Merged

/content endpoint #806

merged 6 commits into from
Aug 11, 2022

Commits on Aug 11, 2022

  1. Moved handling of the "/" URL

    @veloman-yunkan
    veloman-yunkan committed Aug 11, 2022
    Configuration menu
    Copy the full SHA
    a4b1889 View commit details
    Browse the repository at this point in the history

  2. Introduced /content endpoint 

    Book content is now served under /content/book/...

The old access to book content via a top-level URL /book/... is so far
preserved for backward compatibility.

Redirects were changed to use the new URL scheme. Links in the search results
still use the old scheme.
    @veloman-yunkan
    veloman-yunkan committed Aug 11, 2022
    Configuration menu
    Copy the full SHA
    1b1c1e3 View commit details
    Browse the repository at this point in the history

  3. Using /content/... URLs in OPDS output

    @veloman-yunkan
    veloman-yunkan committed Aug 11, 2022
    Configuration menu
    Copy the full SHA
    dc56f82 View commit details
    Browse the repository at this point in the history

  4. Search results now use the /content URL scheme

    @veloman-yunkan
    veloman-yunkan committed Aug 11, 2022
    Configuration menu
    Copy the full SHA
    fd36d11 View commit details
    Browse the repository at this point in the history

  5. More robust handling of endpoint URLs 

    The next goal is to redirect old-style /book/path/to/entry URLs to
/content/book/path/to/entry, which seemed pretty trivial.

However, given the current handling of some endpoint URLs, more work was
required to ensure that invalid endpoint URLs (e.g.  "/random/number" or
"/suggest/fr") are not interpreted as content URLs. Previously, that was
not a user-observable issue, since the result would be an immediate 404
error (except in certain edge cases, like handling the request for
"/random/number" when there is a book with name "random" containing an
article at path "/number"). With redirection of URLs that were assumed
to refer to content a 404 error would be issued for the
transformed URL ("/content/random/number") which may be confusing.

Therefore this change is to ensure the correct routing of endpoint URL
handling.
    @veloman-yunkan
    veloman-yunkan committed Aug 11, 2022
    Configuration menu
    Copy the full SHA
    3b98987 View commit details
    Browse the repository at this point in the history

  6. Redirecting /nonendpoint URLs to /content/nonendpoint

    @veloman-yunkan
    veloman-yunkan committed Aug 11, 2022
    Configuration menu
    Copy the full SHA
    e323dcf View commit details
    Browse the repository at this point in the history