mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 09:05:56 +03:00
[GH-ISSUE #409] Convert all form processing to POST #344
Labels
No labels
📶 WiFi
🕸️ HTTP
Branch
DEV Help Wanted
Discussion
Documentation
ESP32
Example
Good First Issue
Hotfix
In Progress
Incomplete
Needs Feeback
Priority
QA
Question
Task
Upstream/Dependancy
bug
duplicate
enhancement
invalid
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/WiFiManager#344
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tablatronix on GitHub (Aug 30, 2017).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/409
Get is not a secure method of submitting forms on an open ap specifically.
❓ leave url forms as get? but what if inputs get added later etc, not sure how to handle, all post for now.
support GET optionally ( for script based url programming )
the library seems to not care, however we can deny by checking
server->method() == HTTP_GET@tzapu commented on GitHub (Aug 30, 2017):
why not form submissions POST and whatever's not a form submision GET?
if you are using a browser and not the captive portal using the back button becomes a pain in the ass if you navigate between POSTs
@tzapu commented on GitHub (Aug 30, 2017):
the change shouldn't be big either, i guess just changing the form to POST and making sure it gets the params from the POST rather than string, not sure if that part is not transparent anyway
@tzapu commented on GitHub (Aug 30, 2017):
like you ve actually done in your last commit :P
i'll but out, you are a machine :D
@tablatronix commented on GitHub (Aug 30, 2017):
I tested and changed all to post, I think it better than to have to decide which page will have a form on it etc. we can adjust as needed, if it is a problem with browser history.
@tablatronix commented on GitHub (Aug 30, 2017):
So far browser history works as expected
@tablatronix commented on GitHub (Aug 30, 2017):
why not replace form buttons with actual proper links ?
hmm I am now wondering if semantically these should be styled links with hrefs, and only actual forms be forms with inputs... #410