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

Calling directly /archive/123 gives 500 Internal Server Error #1924

Closed
Strubbl opened this issue Apr 14, 2016 · 0 comments
Closed

Calling directly /archive/123 gives 500 Internal Server Error #1924

Strubbl opened this issue Apr 14, 2016 · 0 comments
Labels
Milestone

Comments

@Strubbl
Copy link
Contributor

Strubbl commented Apr 14, 2016

Issue details

If i call directly the URL (without any referer or the like) in my browser, e.g. https://wallabag.domain.de/archive/832
I get the error message in the browser:

Oops! An Error Occurred
The server returned a "500 Internal Server Error".
Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

The log file of wallabag says:

[2016-04-14 21:36:36] request.INFO: Matched route "archive_entry". {"route_parameters":{"_controller":"Wallabag\\CoreBundle\\Controller\\EntryController::toggleArchiveAction","id":"832","_route":"archive_entry"},"request_uri":"https://wallabag.domain.de/archive/832"} []
[2016-04-14 21:36:36] security.DEBUG: Read existing security token from the session. {"key":"_security_secured_area"} []
[2016-04-14 21:36:36] security.DEBUG: User was reloaded from a user provider. {"username":"strubbl","provider":"Symfony\\Bridge\\Doctrine\\Security\\User\\EntityUserProvider"} []
[2016-04-14 21:36:37] request.CRITICAL: Uncaught PHP Exception InvalidArgumentException: "Cannot redirect to an empty URL." at /home/strubbl/git/wallabag/vendor/symfony/symfony/src/Symfony/Component/HttpFoundation/RedirectResponse.php line 76 {"exception":"[object] (InvalidArgumentException(code: 0): Cannot redirect to an empty URL. at /home/strubbl/git/wallabag/vendor/symfony/symfony/src/Symfony/Component/HttpFoundation/RedirectResponse.php:76)"} []
[2016-04-14 21:36:37] security.DEBUG: Stored the security token in the session. {"key":"_security_secured_area"} []

In the end, my article indeed gets archived, but i see this error message. Same with star and delete (and maybe some other function i don't know of).

PS: I found this bug during Android app development, because the app directly calls this URL and compares the response code to 200.

Environment

  • wallabag version (or git revision) that exhibits the issue: 2.0.0
  • How did you install wallabag? Via git clone
  • Last wallabag version that did not exhibit the issue (if applicable): -
  • php version: PHP 5.6.19-0+deb8u1
  • OS: Debian
  • type of hosting (shared or dedicated): dedicated
  • which storage system you choose at install (SQLite, MySQL/MariaDB or PostgreSQL): mysql

Steps to reproduce/test case

  1. open browser
  2. enter url https://wallabag.domain.de/archive/832 (with valid article id of course)
Strubbl added a commit to Strubbl/wallabag-android-app that referenced this issue Apr 14, 2016
v2 functions for addLink, toggleArchive, toggleFavorite and
deleteArticle are working. They give a 500 error at the moment, but this
is reported in wallabag/wallabag#1924
@nicosomb nicosomb added the Bug label Apr 15, 2016
@nicosomb nicosomb added this to the 2.0.2 milestone Apr 15, 2016
nicosomb added a commit that referenced this issue Apr 15, 2016
Strubbl added a commit to Strubbl/wallabag-android-app that referenced this issue Apr 15, 2016
v2 functions for addLink, toggleArchive, toggleFavorite and
deleteArticle are working. They give a 500 error at the moment, but this
is reported in wallabag/wallabag#1924
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants