Bug #455
closed
On initial wizard reload button do not put browser on new assigned ip.
Added by Oscar Francia over 14 years ago.
Updated over 13 years ago.
Description
On initial wizard reload button do not put browser on new ip.
When I was looking at the code when trying to fix the issue with showing the IP address twice in the image link at the end, I thought this might possibly be the case, but I didn't change it because I wasn't sure. I didn't test it at that time because I didn't want to interrupt my connection. Looks like I was right about it, though.
This will not be possible because the new ip is not yet setup in the interface and it need to be added special code to find the correct ip address.
Not sure it is needed.
after hitting reload at the last page in the wizard in 1.2.3, it redirects to the changed IP if you're accessing it using the LAN IP. It should still do that.
Somehow it needs to figure out which interface it was accessed on to redirect to the correct address from the configuration. If the old address no longer exists in the configuration, it may need to find it some other way.
- Status changed from New to Feedback
- % Done changed from 0 to 100
- % Done changed from 100 to 30
The fix is not complete.
Please do it right....
Is this last change something like what you meant?
By the way, this could also be designed to check whether the user changed the host name but is currently accessing by the old host name, though I'm not quite sure how I might go about finding what the old host name was, accurately without false positives. Might be unnecessary because of DNS caching, though.
Except for that I just realized that the DNS rebind check wouldn't allow the old host name by default. This needs a new ticket of its own.
What is the needed feedback? I want to test fixes but there does not seems to be neither a fix nor a question
// rancor
- Status changed from Feedback to Closed
- Target version deleted (
2.0)
Also available in: Atom
PDF