HTTP POST for reading (rather than HTTP GET)

REST design principles article sum-up👇👇👇

I have lately been arguing about API REST Design good practices, and about the possibility to use a POST for reading data (due to URL peculiarity with special characters).

And my opinion was that a good practice can be infringed if it remains exceptional.

Here an answer from stack which complies with mine:

"𝐼 𝑢𝑠𝑒 𝑃𝑂𝑆𝑇 𝑏𝑜𝑑𝑦 𝑓𝑜𝑟 𝑎𝑛𝑦𝑡ℎ𝑖𝑛𝑔 𝑛𝑜𝑛-𝑡𝑟𝑖𝑣𝑖𝑎𝑙 𝑎𝑛𝑑 𝑙𝑖𝑛𝑒-𝑜𝑓-𝑏𝑢𝑠𝑖𝑛𝑒𝑠𝑠 𝑎𝑝𝑝𝑠 𝑓𝑜𝑟 𝑡ℎ𝑒𝑠𝑒 𝑟𝑒𝑎𝑠𝑜𝑛𝑠:

𝑆𝑒𝑐𝑢𝑟𝑖𝑡𝑦 - 𝐼𝑓 𝑤𝑒 𝑢𝑠𝑒 𝐺𝐸𝑇 𝑤𝑖𝑡ℎ 𝑞𝑢𝑒𝑟𝑦 𝑠𝑡𝑟𝑖𝑛𝑔𝑠 𝑎𝑛𝑑 ℎ𝑡𝑡𝑝𝑠, 𝑡ℎ𝑒 𝑞𝑢𝑒𝑟𝑦 𝑠𝑡𝑟𝑖𝑛𝑔𝑠 𝑐𝑎𝑛 𝑏𝑒 𝑠𝑎𝑣𝑒𝑑 𝑖𝑛 𝑠𝑒𝑟𝑣𝑒𝑟 𝑙𝑜𝑔𝑠 𝑎𝑛𝑑 𝑓𝑜𝑟𝑤𝑎𝑟𝑑𝑒𝑑 𝑎𝑠 𝑟𝑒𝑓𝑒𝑟𝑟𝑎𝑙 𝑙𝑖𝑛𝑘𝑠. 𝐵𝑜𝑡ℎ 𝑜𝑓 𝑡ℎ𝑒𝑠𝑒 𝑎𝑟𝑒 𝑛𝑜𝑤 𝑣𝑖𝑠𝑖𝑏𝑙𝑒 𝑏𝑦 𝑠𝑒𝑟𝑣𝑒𝑟/𝑛𝑒𝑡𝑤𝑜𝑟𝑘 𝑎𝑑𝑚𝑖𝑛𝑠 𝑎𝑛𝑑 𝑡ℎ𝑒 𝑛𝑒𝑥𝑡 𝑑𝑜𝑚𝑎𝑖𝑛 𝑡ℎ𝑒 𝑢𝑠𝑒𝑟 𝑤𝑒𝑛𝑡 𝑡𝑜 𝑎𝑓𝑡𝑒𝑟 𝑙𝑒𝑎𝑣𝑖𝑛𝑔 𝑦𝑜𝑢𝑟 𝑎𝑝𝑝. 𝑆𝑜 𝑖𝑓 𝑤𝑒 𝑠𝑒𝑛𝑑 𝑎 𝑞𝑢𝑒𝑟𝑦 𝑐𝑜𝑛𝑡𝑎𝑖𝑛𝑖𝑛𝑔 𝑐𝑜𝑛𝑓𝑖𝑑𝑒𝑛𝑡𝑖𝑎𝑙 𝑃𝐼𝐼 𝑑𝑎𝑡𝑎 𝑠𝑢𝑐ℎ 𝑎𝑠 𝑎 𝑐𝑢𝑠𝑡𝑜𝑚𝑒𝑟'𝑠 𝑛𝑎𝑚𝑒 𝑡ℎ𝑖𝑠 𝑚𝑎𝑦 𝑛𝑜𝑡 𝑏𝑒 𝑑𝑒𝑠𝑖𝑟𝑒𝑑.

𝑈𝑅𝐿 𝑚𝑎𝑥𝑖𝑚𝑢𝑚 𝑙𝑒𝑛𝑔𝑡ℎ - 𝑁𝑜𝑡 𝑎 𝑏𝑖𝑔 𝑖𝑠𝑠𝑢𝑒, 𝑏𝑢𝑡 𝑠𝑜𝑚𝑒 𝑏𝑟𝑜𝑤𝑠𝑒𝑟𝑠 ℎ𝑎𝑣𝑒 𝑎 𝑙𝑖𝑚𝑖𝑡 𝑜𝑛 𝑡ℎ𝑒 𝑙𝑒𝑛𝑔𝑡ℎ. 𝑆𝑜 𝑖𝑓 𝑤𝑒 ℎ𝑎𝑣𝑒 𝑠𝑒𝑣𝑒𝑟𝑎𝑙 𝑖𝑡𝑒𝑚𝑠 𝑖𝑛 𝑜𝑢𝑟 𝑈𝑅𝐿 𝑙𝑖𝑘𝑒 𝑞𝑢𝑒𝑟𝑦, 𝑝𝑎𝑔𝑖𝑛𝑔, 𝑓𝑖𝑒𝑙𝑑𝑠 𝑡𝑜 𝑟𝑒𝑡𝑢𝑟𝑛, 𝑒𝑡𝑐....

𝑃𝑂𝑆𝑇 𝑖𝑠 𝑛𝑜𝑡 𝑐𝑎𝑐ℎ𝑒𝑑 𝑏𝑦 𝑑𝑒𝑓𝑎𝑢𝑙𝑡. 𝑆𝑜𝑚𝑒 𝑠𝑎𝑦 𝑐𝑎𝑐ℎ𝑖𝑛𝑔 𝑖𝑠 𝑑𝑒𝑠𝑖𝑟𝑒𝑑; ℎ𝑜𝑤𝑒𝑣𝑒𝑟, ℎ𝑜𝑤 𝑜𝑓𝑡𝑒𝑛 𝑖𝑠 𝑡ℎ𝑎𝑡 𝑒𝑥𝑎𝑐𝑡 𝑠𝑎𝑚𝑒 𝑠𝑒𝑡 𝑜𝑓 𝑠𝑒𝑎𝑟𝑐ℎ 𝑐𝑟𝑖𝑡𝑒𝑟𝑖𝑎 𝑓𝑜𝑟 𝑡ℎ𝑎𝑡 𝑒𝑥𝑎𝑐𝑡 𝑜𝑏𝑗𝑒𝑐𝑡 𝑓𝑜𝑟 𝑡ℎ𝑎𝑡 𝑒𝑥𝑎𝑐𝑡 𝑐𝑢𝑠𝑡𝑜𝑚𝑒𝑟 𝑔𝑜𝑖𝑛𝑔 𝑡𝑜 𝑜𝑐𝑐𝑢𝑟 𝑏𝑒𝑓𝑜𝑟𝑒 𝑡ℎ𝑒 𝑐𝑎𝑐ℎ𝑒 𝑡𝑖𝑚𝑒𝑠 𝑜𝑢𝑡 𝑎𝑛𝑦𝑤𝑎𝑦?

𝐵𝑇𝑊, 𝐼 𝑎𝑙𝑠𝑜 𝑝𝑢𝑡 𝑡ℎ𝑒 𝑓𝑖𝑒𝑙𝑑𝑠 𝑡𝑜 𝑟𝑒𝑡𝑢𝑟𝑛 𝑖𝑛 𝑚𝑦 𝑃𝑂𝑆𝑇 𝑏𝑜𝑑𝑦 𝑎𝑠 𝐼 𝑚𝑎𝑦 𝑛𝑜𝑡 𝑤𝑖𝑠ℎ 𝑡𝑜 𝑒𝑥𝑝𝑜𝑠𝑒 𝑚𝑦 𝑓𝑖𝑒𝑙𝑑 𝑛𝑎𝑚𝑒𝑠. 𝑆𝑒𝑐𝑢𝑟𝑖𝑡𝑦 𝑖𝑠 𝑙𝑖𝑘𝑒 𝑎𝑛 𝑜𝑛𝑖𝑜𝑛; 𝑖𝑡 ℎ𝑎𝑠 𝑚𝑎𝑛𝑦 𝑙𝑎𝑦𝑒𝑟𝑠 𝑎𝑛𝑑 𝑚𝑎𝑘𝑒𝑠 𝑢𝑠 𝑐𝑟𝑦!"