# Looking for feedback about new Early Hints standard

**URL:** <https://community.nginx.org/t/looking-for-feedback-about-new-early-hints-standard/1757>\
**Category:** Community Showcase\
**Tags:** blog\
**Created:** [April 2, 2025, 7:23pm UTC](https://community.nginx.org/t/looking-for-feedback-about-new-early-hints-standard/1757 "2025-04-02T19:23:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![s.miller](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/s.miller/32/39_2.png) [@s.miller](https://community.nginx.org/u/s.miller)\
**Post date:** [April 2, 2025, 7:23pm UTC](https://community.nginx.org/t/looking-for-feedback-about-new-early-hints-standard/1757/1 "2025-04-02T19:23:47Z")

</div>

In a post on [blog.nginx.org](http://blog.nginx.org), Nick Shadrin is **requesting** feedback on the new Early Hints standard, which allows servers to send an informational response with the HTTP status code 103.

Please **respond** with your thoughts here or create your own topic about it on the forum!

Read the blog post: [We Request Your Feedback for Early Hints – NGINX Community Blog](https://blog.nginx.org/blog/we-request-your-feedback-for-early-hints)

 ![](https://d7a5pgbt9tjl6.cloudfront.net/original/2X/e/eed3dfb37d6ad458b3a8e95f22f2c660737442ce.png)