> Some background: HTTP and IPP services in printers include absolute URIs in
> the content they return. For IPP this can be http/https URLs to the printer's
> web page, ICC profiles, and other resources, along with the ipp/ipps URIs
> that the printer supports. For HTTP the most common are https URLs for
> "secure" areas of the printer's web interface. Because a printer is often
> known by multiple names and addresses ("printer.local.",
> "printer.example.com.", 192.168.0.100, fe80::1234, etc.), the implementation
> guidance (and in IPP Everywhere, this is a conformance requirement) is that
> the server use the HTTP Host header provided in the request in the
> host/address field of its responses, subject to the usual security
> considerations (SHOULD validate Host value, etc.) This allows the client to
> use the name or address it can resolve/connect to and makes sure that the
> printer-generated absolute URIs lead back to same printer.
> All of this falls apart with link-local addresses and RFC 6874. Because the
> client is required to remove the zoneid from the outgoing request, the URIs
> it gets back from the server are no longer "reachable".
Do you have this problem only with link local addresses, or with some other
addresses as well?
-- Christian Huitema
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
