Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[scoman81]

I just upgraded my DNS-320 to 2.02, and this bug just showed up as a result.

My 320's login page requires a port number (since I have a real web server, too), so I have port 9116 forwarding to the 320. So the URL is (e.g.) "www.mydomain.com:9116" This now fails under 2.02, in this way:

1. Login page is loaded in browser (http://www.mydomain.com:9116)
2. Login credentials are submitted, and browser sits, waiting, for about 20 seconds.
3. A page not found error is displayed. The page is (e.g.) http://www.mydomain.com/web/home.html

As you can see, the port number has been removed on the authentication redirect, and as such, the redirected URL is invalid.

Since the cookie is set (or whatever they're using), simply adding the port number back in does load the redirect page correctly. But this broke in 2.02 ... it was working fine in 2.00. (I had to upgrade to get printing to work, and now I can't go back ... )

Help?

[albert]

IIRC, this is a known bug in 2.02 and has since been removed from download site in certain region. The only solution is to upgrade to 2.03b1 (beta) or wait for stable release.