<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the <a href="https://github.com/zeit/next.js/issues">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h2 dir="auto">Expected Behavior</h2>


<p dir="auto">An error page is shown when the react rendering tree throw an error in production</p>
<h2 dir="auto">Current Behavior</h2>


<p dir="auto">A blank page is shown when the react rendering tree throw an error in production</p>
<h2 dir="auto">Steps to Reproduce (for bugs)</h2>


<ol dir="auto">
<li>Render a page server side with no errors</li>
<li>Render a page client side with no errors</li>
<li>Navigate to a page that throw inside the render method.</li>
</ol>
<h2 dir="auto">Context</h2>


<p dir="auto">I'm not 100% sure, but I think that such logic was present with v3.<br>
It could have been removed with <a class="commit-link" href="https://github.com/vercel/next.js/commit/d19cc975f4be6bf1d1ef205950b5749f5e735d78#diff-1858c8296dd2b642c74271609cf701e7L40"><tt>d19cc97</tt>#diff-1858c8296dd2b642c74271609cf701e7L40</a>.</p>
<h2 dir="auto">Your Environment</h2>

<table role="table">
<thead>
<tr>
<th>Tech</th>
<th>Version</th>
</tr>
</thead>
<tbody>
<tr>
<td>next</td>
<td>v4.0.2</td>
</tr>
<tr>
<td>node</td>
<td>v8.1.4</td>
</tr>
<tr>
<td>OS</td>
<td>MacOs</td>
</tr>
<tr>
<td>browser</td>
<td>Chrome</td>
</tr>
</tbody>
</table>
<p dir="auto">It's a good idea to create immutable static assets, such as images, and set the cache to never expire. It appears that Next.js does a good job of this for the JavaScript files, but it would be great to document a solution for CDN static assets.</p>


<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the <a href="https://github.com/zeit/next.js/issues">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h2 dir="auto">Expected Behavior</h2>


<p dir="auto">Next.js build assets get served from <code class="notranslate">_next/&lt;some uuid&gt;/&lt;asset path&gt;</code>. Perhaps a similar solution could work for static assets as well? We could supply instructions for setting up common reverse proxies to serve the static assets properly (nginx, haproxy).</p>
<h2 dir="auto">Current Behavior</h2>


<p dir="auto">Static assets always get served from the same URL, which forces users to roll their own cache-invalidation solution for static content, even though perfectly usable cache-invalidation is already built-in to Next.js.</p>
<h2 dir="auto">Context</h2>


<p dir="auto">We recently rolled a new version of one of our apps into production. Everything worked great, but it served up the old image assets, which may cause a lot of confusion.</p>
<p dir="auto">Presumably, a solution to this problem is needed for every application ever made. We should make sure it's covered in the Next.js documentation.</p>
<h2 dir="auto">Your Environment</h2>
<p dir="auto">No bug. Just requesting documentation.</p>