[GH-ISSUE #8] some fritz boxes only can handle 1 update url #7

Closed
opened 2026-02-26 09:34:52 +03:00 by kerem · 3 comments
Owner

Originally created by @ThomasWaldmann on GitHub (Oct 22, 2013).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/8

ThomasWaldmann wrote:
My fritzbox 6360 from "Kabel BW" (Fritz!OS 05.50) can only handle 1 URL.

if one enters 2 URLs, separated by a space, this happens:

2013-09-30 12:51:21 [15897] [DEBUG] GET /nic/update%20http:/ipv6.nsupdate.info/nic/update

It works correctly with 1 URL, so documentation should get updated to first try 1 URL only and the 2 URLs for fritz boxes.

If it works ok for 1, and does 404 (see fritzbox log) for 2, it can't handle 2.

Originally created by @ThomasWaldmann on GitHub (Oct 22, 2013). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/8 ThomasWaldmann wrote: My fritzbox 6360 from "Kabel BW" (Fritz!OS 05.50) can only handle 1 URL. if one enters 2 URLs, separated by a space, this happens: ``` 2013-09-30 12:51:21 [15897] [DEBUG] GET /nic/update%20http:/ipv6.nsupdate.info/nic/update ``` It works correctly with 1 URL, so documentation should get updated to first try 1 URL only and the 2 URLs for fritz boxes. If it works ok for 1, and does 404 (see fritzbox log) for 2, it can't handle 2.
kerem closed this issue 2026-02-26 09:34:52 +03:00
Author
Owner

@ThomasWaldmann commented on GitHub (Oct 22, 2013):

ThomasWaldmann wrote:
the fritzbox 6360 works correctly.

due to copy&paste, there was a leading blank at the begining of the urls field.

as the fritzbox firmware does not strip leading/trailing blanks, and only splits on first blank, it goes totally wrong in that case...

<!-- gh-comment-id:26768333 --> @ThomasWaldmann commented on GitHub (Oct 22, 2013): ThomasWaldmann wrote: the fritzbox 6360 works correctly. due to copy&paste, there was a leading blank at the begining of the urls field. as the fritzbox firmware does not strip leading/trailing blanks, and only splits on first blank, it goes totally wrong in that case...
Author
Owner

@ThomasWaldmann commented on GitHub (Oct 22, 2013):

ThomasWaldmann wrote:
hmm, if one selects the text line with a double click, it looks ok, one does not see a leading blank.
but if one copies & pastes that, it is there.

in the html, there is leading whitespace, maybe that matters - try to avoid that.

<!-- gh-comment-id:26768334 --> @ThomasWaldmann commented on GitHub (Oct 22, 2013): ThomasWaldmann wrote: hmm, if one selects the text line with a double click, it looks ok, one does not see a leading blank. but if one copies & pastes that, it is there. in the html, there is leading whitespace, maybe that matters - try to avoid that.
Author
Owner

@ThomasWaldmann commented on GitHub (Oct 22, 2013):

ThomasWaldmann wrote:
fixed the html in the new organization repo, copy&paste now does not sneak in leading/trailing blanks any more.

<!-- gh-comment-id:26768335 --> @ThomasWaldmann commented on GitHub (Oct 22, 2013): ThomasWaldmann wrote: fixed the html in the new organization repo, copy&paste now does not sneak in leading/trailing blanks any more.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nsupdate.info-nsupdate-info#7
No description provided.