• Resolved inevitability

    (@inevitability)


    When someone tries to remote authorize a premium RSS and fails, it just returns “unauthorized.”

    Is there a way to have it do a temporary redirect to a different RSS? Ideally one that has an MP3 of me telling them that their username or password is incorrectly entered.

    This would save me SO MUCH tech support time. Lol.

Viewing 1 replies (of 1 total)
  • Plugin Contributor Angelo Mandato

    (@amandato)

    Hello @inevitability,

    Unfortunately it would not work. It is hard to explain but I will try. The problem is with the HTTP requirements for authorization of using the 401 HTTP status code to prompt for authentication. First your applications requests the URL without knowing the application needs to provide a user name and password. When the browser or app gets the returned 401 unauthorized header, it then knows to pop-up a dialog prompting for a user name and password. If your server sent a 301 redirect back instead of the 401, the application would never have known to prompt the user for a username and password. You cannot mix or send both HTTP status codes unfortunately, you must only send one. In other words, if you want to require the authentication header on a specific URL, you must send back a 401 unauthorized header when the user name/password is incorrect or not present.

    Thanks,
    Angelo

Viewing 1 replies (of 1 total)

The topic ‘Redirect failed RSS authorizations’ is closed to new replies.