You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the web, live navigation has the following behavior:
redirect re-establish socket connection and re-mount the liveview
push_navigate re-use existing socket connection and re-mount the liveview
push_patch re-use existing socket connection and existing liveview (no mount/3, only handle_params)
However, on native our redirect event re-uses the existing socket connection rather than re-establishing it. I think this could be a potential security risk, or at the very least, doesn't match what developers will expect.
The text was updated successfully, but these errors were encountered:
On the web, live navigation has the following behavior:
redirect
re-establish socket connection and re-mount the liveviewpush_navigate
re-use existing socket connection and re-mount the liveviewpush_patch
re-use existing socket connection and existing liveview (nomount/3
, only handle_params)However, on native our
redirect
event re-uses the existing socket connection rather than re-establishing it. I think this could be a potential security risk, or at the very least, doesn't match what developers will expect.The text was updated successfully, but these errors were encountered: