Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://ngmx.com/users/sindarina/statuses/110598199724246507">Sindarina, Edge Case Detective (sindarina@ngmx.com)'s status on Saturday, 24-Jun-2023 21:28:58 JST</a><a href="https://ngmx.com/@sindarina" title="sindarina@ngmx.com"><img src="https://gnusocial.jp/avatar/102235-48-20230329174946.webp" width="48" height="48" alt="Sindarina, Edge Case Detective" style="position: absolute; left: 0; top: 0;">Sindarina, Edge Case Detective</a></section><article><p>Since I keep seeing developers use ‘pretty’ IP addresses like ’1.2.3.4’ in example configurations; a reminder that you MUST NOT use publicly routable addresses that you do not control in your code.</p><p>Instead, use one of the available 'TEST-NET' IPv4 or IPv6 ranges documented in RFC 6890;</p><p>192.0.2.0/24<br>198.51.100.0/24<br>203.0.113.0/24</p><p>❌ 1.2.3.4<br>✅ 192.0.2.4</p><p>and for IPv6;</p><p>✅ 2001:db8::/32</p><p>Pass it on to all of your fellow developers, documentation writers, and so forth.</p><p>Full RFC for special purpose addresses;</p><p><a href="https://datatracker.ietf.org/doc/rfc6890/" rel="nofollow noreferrer">https://datatracker.ietf.org/doc/rfc6890/</a></p><p>Reserved for documentation, IPv4 and IPv6;</p><p><a href="https://datatracker.ietf.org/doc/rfc5737/" rel="nofollow noreferrer">https://datatracker.ietf.org/doc/rfc5737/</a><br><a href="https://datatracker.ietf.org/doc/rfc3849/" rel="nofollow noreferrer">https://datatracker.ietf.org/doc/rfc3849/</a></p><p>1/ 🧵</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/1686462#notice-3317963">In conversation</a><time datetime="2023-06-24T21:28:58+09:00" title="Saturday, 24-Jun-2023 21:28:58 JST">Saturday, 24-Jun-2023 21:28:58 JST</time> <span>from <span><a href="https://ngmx.com/@sindarina/110598199724246507" rel="external" title="Sent from ngmx.com via ActivityPub">ngmx.com</a></span></span><a href="https://ngmx.com/@sindarina/110598199724246507">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/1163811">Untitled attachment</a></label><br></li><li><article><header><div>Domain not in remote thumbnail source whitelist: www.ietf.org</div><h5><a href="https://datatracker.ietf.org/doc/rfc5737/">RFC 5737: IPv4 Address Blocks Reserved for Documentation</a></h5><div> from <span>Leo Vegoda</span></div></header><div>Three IPv4 unicast address blocks are reserved for use in examples in specifications and other documents. This document describes the use of these blocks. This document is not an Internet Standards Track specification; it is published for informational purposes.</div><footer></footer></article></li><li><label><a rel="external" href="https://gnusocial.jp/attachment/1163813">Untitled attachment</a></label><br></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Sindarina, Edge Case Detective (sindarina@ngmx.com)'s status on Saturday, 24-Jun-2023 21:28:58 JST Sindarina, Edge Case Detective
Since I keep seeing developers use ‘pretty’ IP addresses like ’1.2.3.4’ in example configurations; a reminder that you MUST NOT use publicly routable addresses that you do not control in your code.
Instead, use one of the available 'TEST-NET' IPv4 or IPv6 ranges documented in RFC 6890;
192.0.2.0/24
198.51.100.0/24
203.0.113.0/24
❌ 1.2.3.4
✅ 192.0.2.4
and for IPv6;
✅ 2001:db8::/32
Pass it on to all of your fellow developers, documentation writers, and so forth.
Full RFC for special purpose addresses;
https://datatracker.ietf.org/doc/rfc6890/
Reserved for documentation, IPv4 and IPv6;
https://datatracker.ietf.org/doc/rfc5737/
https://datatracker.ietf.org/doc/rfc3849/
1/ 🧵
In conversationSaturday, 24-Jun-2023 21:28:58 JST from ngmx.compermalink
Attachments
1. Untitled attachment
2. Domain not in remote thumbnail source whitelist: www.ietf.org
  RFC 5737: IPv4 Address Blocks Reserved for Documentation
  from Leo Vegoda
  Three IPv4 unicast address blocks are reserved for use in examples in specifications and other documents. This document describes the use of these blocks. This document is not an Internet Standards Track specification; it is published for informational purposes.
3. Untitled attachment

Public

Embed Notice

HTML Code

Corresponding Notice