mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 17:15:53 +03:00
[GH-ISSUE #82] password issue #60
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#60
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 @ratzl on GitHub (Jan 26, 2016).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/82
When I try to enter a password in the configuration page, it's not working when the
password contains the + sign
example password: +Test- (not working)
example password: -Test- ( working)
@shirish47 commented on GitHub (Jan 27, 2016):
well I am not sure whats the problem with me when I try to connect after configuration it fails even though password is correct... it seems that there is some extra character.. or something .. my password contains alphabets and a number and "(" ")"..... previous libraries used to work...
@tzapu commented on GitHub (Jan 27, 2016):
thanks for the reports,
@ratzl & @shirish47 could you please let me know how your password ends up in the url string after save? it should be in the p= var
@shirish47 commented on GitHub (Jan 27, 2016):
yes it comes that way ..accept "(" turn to %28 and ")" to %29 I think that is normal even when wifi trys to connect it shows that password correctly in the debug msgs.
@shirish47 commented on GitHub (Jan 27, 2016):
when I reset it I get this ..
WM: AutoConnect
*WM: Reading SSID
*WM: SSID:
*WM: UNICORN
*WM: Reading Password
*WM: Password:************ // it shows correct password but I removed it here
*WM: Connecting as wifi client...
*WM: Connection result:
*WM: 1
*WM:
*WM: Configuring access point...
*WM: AutoConnectAP
*WM: AP IP address:
*WM: 192.168.4.1
*WM: HTTP server started
@tzapu commented on GitHub (Jan 27, 2016):
are you using 0.6 release ? or latest from github
what esp8266 core version are you using?
@shirish47 commented on GitHub (Jan 27, 2016):
version 2 for esp8266 core and for this library its 0.6
@ratzl commented on GitHub (Jan 28, 2016):
*WM:
*WM: AutoConnect
*WM: Reading SSID
*WM: SSID:
*WM: rapi-wlan
*WM: Reading Password
*WM: Password: -12Li5a3- //password was -12Li5a3-
*WM: Connecting as wifi client...
*WM: Connection result:
*WM: 3
*WM: IP Address:
*WM: 134.103.68.138
*WM:
*WM: AutoConnect
*WM: Reading SSID
*WM: SSID:
*WM: rapi-wlan
*WM: Reading Password
*WM: Password: 12Li5a3- //password was +12Li5a3-
*WM: Connecting as wifi client...
*WM: Connection result:
*WM: 4
*WM:
*WM: Configuring access point...
*WM: ESP125778
*WM: AP IP address:
*WM: 192.168.4.1
*WM: HTTP server started
@domonetic commented on GitHub (Jan 28, 2016):
What value returns getPassword()?
there may be a bug in the password storage from portal
@domonetic commented on GitHub (Jan 28, 2016):
here the error:
in urldecore if char == '+'
if (*src == '+') {
decoded += ' ';
*src++;
} else {
@shirish47 commented on GitHub (Jan 29, 2016):
ok can you explain the error? is it encoding it before saving to file and then decoding it and having trouble. but my password does not include any other characters other than "(" and ")"...
@shirish47 commented on GitHub (Jan 29, 2016):
this library's old (0.5) version works fine with my code.
@tzapu commented on GitHub (Jan 29, 2016):
guys, sorry about this, i m away until middle of next week and can only look/do at minor stuff, will try looking more next week
@shirish47 commented on GitHub (Jan 29, 2016):
no problem buddy .. thanks :)
@domonetic commented on GitHub (Jan 29, 2016):
@shirish47
I really do not understand that urldecode , but I think that's the problem with special characters.
@shirish47 commented on GitHub (Jan 29, 2016):
ya its I think something related to Base 64 I am not sure .. but I had similar issue with base 64 ..one of servers were not accepting my data after encoded to b64, because of null termination.. and its difficult to handle strings in C without null termination.
@tzapu commented on GitHub (Feb 4, 2016):
i think i removed the + sign at some point for a specific purpose that i now can t remember :(
i think it may have been messing with spaces in ssids ... really can t remember
i think there might be a new version of url decoding coming soon as part of the core... i ll look into adding that
@tzapu commented on GitHub (Feb 4, 2016):
hi all, this should be sorted in 0.9
i was double decoding as the server lib was already doing that
please test and reopen if needed