Pow session path not working

hassamali

i tried to register with pow route its working but when i am trying to sign out with pow session with method delete its not working and complaining

no route found for GET /session (QazalbashWeb.Router)

with the pow and session these are only available routes

pow_session_path  GET     /session/new                             Pow.Phoenix.SessionController :new
pow_session_path  POST    /session                                 Pow.Phoenix.SessionController :create
pow_session_path  DELETE  /session                                 Pow.Phoenix.SessionController :delete

What i am doing on the front-end is this, Register is working fine but not sign out

<%= link "Sign Out", to: Routes.pow_session_path(@conn, :delete), method: :delete  %>
<%= link "Register", to: Routes.pow_registration_path(@conn, :new) %>

7 comments

/phoenix #pow-router

0 2075 7

2023-04-23 14:21:31 UTC

Showing Posts 1 to 7

Show Best Posts
Show All (oldest first)
Show All (newest first)

sfusato

It’s not complaining about the sign out, but rather about where you are redirecting after it.

How does your after_sign_out_path look like?

Post #1

hassamali

there is no after sign out path its a library + fresh installation of the project it will redirect it to the homepage after sign out, but i checked the session its not signed out user is still sign in

Post #2

BobbyMcWho

What does your router.ex look like?

Post #3

wowlixir

I’m having the same issue, except the behavior isn’t always the same. Sometimes it redirects to /, sometimes to /session/new, and sometimes to /session. When it redirects to /session the error appears and signing out fails. In other redirections signing out succeeds.

My router.ex (I’d like to take this opportunity to ask if there’s anything I can improve on this file ):

defmodule MyAppWeb.Router do
  use MyAppWeb, :router
  use Pow.Phoenix.Router
  use Pow.Extension.Phoenix.Router,
    extensions: [PowPersistentSession]

  pipeline :browser do
    plug :accepts, ["html"]
    plug :fetch_session
    plug :fetch_live_flash
    plug :protect_from_forgery
    plug :put_secure_browser_headers
  end

  pipeline :protected do
    plug Pow.Plug.RequireAuthenticated,
      error_handler: Pow.Phoenix.PlugErrorHandler
  end

  pipe_through :browser
  get "/", MyAppWeb.PageController, :index

  scope "/" do
    pow_session_routes()
    pow_extension_routes()
  end

  scope "/", as: "pow" do
    pipe_through :protected
    # https://github.com/danschultzer/pow/blob/master/guides/disable_registration.md
    resources "/registration", Pow.Phoenix.RegistrationController, only: [:edit, :update],
                               singleton: true
  end

  scope "/" do
    pipe_through :protected
    resources "/articles", MyAppWeb.ArticleController, param: "slug", except: [:index, :show]
    resources "/categories", MyAppWeb.CategoryController
  end

  scope "/" do
    resources "/articles", MyAppWeb.ArticleController, param: "slug", only: [:index, :show]
  end

end

Post #4

hassamali

Make sure that you got import "phoenix_html" in your JS, and restart the server if necessary. This is just a default Phoenix HTML anchor link, and will work as long as the JS is enabled and priv/static/phoenix_html.js has been loaded into your build tools.

Post #5

wowlixir

Hmm, how do I know if that is the case? I just checked and I do have import "phoenix_html" in my app.js (which is loaded in my layout template file), as well as "dependencies": { "phoenix": "file:../deps/phoenix", "phoenix_html": "file:../deps/phoenix_html" } in my package.json, but I don’t see phoenix_html.js in my priv/static.

Edit: Oh, if you mean deps/phoenix_html/priv/static/phoenix_html.js, then yes, it was already there.

Post #6

joe

For me the problem originated in having a PWA. Somehow the POST requests were transformed to GET requests because it was trying to open them in the other (native) app. Unfortunately that behaviour is only present if firefox is my default browser on Android. So the only workaround I found was to make Chrome the default browser again.

Post #7

— All posts loaded —