SPWF01SA and SSID with spaces / special characters?

[tuukka]

Posted on December 30, 2014 at 09:05

Hi,

we're using the SPWF01SA's internal web form (''SPWF01 First Config'') to setup Wi-Fi access.

Otherwise it works fine, but when trying to make it connect to a Wi-Fi network that has spaces or special characters in SSID, connection fails.

Is this normal, and is there a workaround for this existing?

Best regards,

TA

#wi-fi #ssid

[Gerardo GALLUCCI]

Posted on December 31, 2014 at 12:29

Hi,

yes, it is a normal behavior.

Since ''First Config'' is based on HTTP Get Method, and since HTTP Get Method is not able to manage all characters, so ''First Config'' engine is not able to catch special characters from the remote host.

From RFC3986: Characters that are allowed in a URI but do not have a reserved purpose are called unreserved. These include uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde.

unreserved = ALPHA / DIGIT / ''-'' / ''.'' / ''_'' / ''~''

If you want to implement a workaround:

- open a socket server on port 80, and manage reserved characters (encoded as %number). For example, 

''%20'' is the percent-encoding for the binary octet

  ''00100000'' (ABNF: %x20), which in US-ASCII corresponds to the space

   character (SP).

- If you can avoid remote browser, use a your own socket client on some port. This way, decoding is not needed. Every sent character, is received without encode/decode.

- Another (maybe more simple) workaround: use the ''Output Demo'' to push parameters, but (again here) decode %number received.

Hope workarounds are fine.

jerry