Changes

The NZone browser interface is similar to the regular [[Internet Browser]], the browser engine used here is completely different however. Unlike the regular [[Internet Browser]] which uses the socket/SSL services directly, the Nintendo Zone application uses the [[HTTP_Services|HTTP]] service instead.

The NZone browser interface is similar to the regular [[Internet Browser]], the browser engine used here is completely different however. Unlike the regular [[Internet Browser]] which uses the socket/SSL services directly, the Nintendo Zone application uses the [[HTTP_Services|HTTP]] service instead.

The NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where 3DS will only "detect" NZone /w NZone icon blinking/enabled when the beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i) NZone, but only if the NZone title is already enabled. With DS(i) beacons, 3DS connects to Internet but the NZone icon will not blink. However the NZone title will still work once launched. Different URL params are sent to the to the server than DSi, sending the wrong params via curl results in an error page being returned.

The 3DS NZone application immediately uses [[NIMS:CheckSysupdateAvailableSOAP]] once connected to the NZone AP, if an update is available and the user selects "Cancel" in the displayed dialog, the application will stop using the wifi AP.

The 3DS NZone application immediately uses [[NIMS:CheckSysupdateAvailableSOAP]] once connected to the NZone AP, if an update is available and the user selects "Cancel" in the displayed dialog, the application will stop using the wifi AP.

The user-agent used by the Nintendo Zone application is "NintendoZoneViewer/3.1". The URL parameters sent to the dsdl.* HTTPS server are the same as DSi(besides the value of the console-type parameter and the "ver" parameter value), except 3DS also sends additional headers in the request using the same data sent in the URL parameters. The zonebnr server requires three more request headers(extra URL parameters are not needed here), the first of these three headers is "ZoneUserID" where the unknown value is 16 hex-digits(8-bytes in binary). The last two headers of these additional three headers contain data which was originally sent with the dsdl server URL parameters.

3D stereoscopic videos are supported via html "<media>" tags, for 3D videos the "mediatype" attribute is set to "3D". This uses Mobiclip with file extension .moflex, the magic number from the first word in the video file is 0xabaa324c(little-endian).

The NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where 3DS will only "detect" NZone /w NZone icon blinking/enabled when the beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i) NZone, but only if the NZone title is already enabled. With DS(i) beacons, 3DS connects to Internet but the NZone icon will not blink. However the NZone title will still work once launched.

=== Beacon payload format ===

=== Beacon payload format ===