<p dir="auto"><strong>I'm submitting a ...</strong>  (check one with "x")</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[ ] bug report =&gt; search github for a similar issue or PR before submitting
[x] feature request
[ ] support request =&gt; Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question"><pre class="notranslate"><code class="notranslate">[ ] bug report =&gt; search github for a similar issue or PR before submitting
[x] feature request
[ ] support request =&gt; Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre></div>
<p dir="auto"><strong>Current behavior</strong><br>
When navigating forward and then back, the scroll position is lost.</p>
<p dir="auto"><strong>Expected/desired behavior</strong><br>
When navigating on an extensive list of items, the user scrolls down the list and click on some item. The app activates the next route/component which shows the product details. If the user decides do navigate back, the page does not scroll to the previous point.</p>
<p dir="auto"><strong>Reproduction of the problem</strong></p>
<p dir="auto">Live example:  <a href="http://plnkr.co/edit/vUROPirs5tjklyBw6t4H?p=preview" rel="nofollow">http://plnkr.co/edit/vUROPirs5tjklyBw6t4H?p=preview</a><br>
step 1 - first, adjust browser zoom until heroes from the hero list disappear<br>
step 2 - scroll down to the end of the page<br>
step 3 - click on "RubberMan"<br>
step 4 - click on the back button either on the browser or the component<br>
step 5 - the page is not scrolled to the same position of stop 2</p>
<p dir="auto"><strong>What is the expected behavior?</strong><br>
The browser should scroll to the previous position like it happens in any non-single page application.</p>
<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong><br>
It should be considered a bug that can reduce the level of the user experience.</p>
<p dir="auto"><strong>Please tell us about your environment:</strong></p>
<ul dir="auto">
<li><strong>Angular version:</strong> 2.0.0-rc.4</li>
<li><strong>Browser:</strong> [all]</li>
<li><strong>Language:</strong> [TypeScript 1.8 | ES5]</li>
</ul>
<p dir="auto"><strong>I'm submitting a ...</strong>  (check one with "x")</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[x] bug report
[ ] feature request
[ ] support request =&gt; Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question"><pre class="notranslate"><code class="notranslate">[x] bug report
[ ] feature request
[ ] support request =&gt; Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre></div>
<p dir="auto"><strong>Current behavior</strong><br>
Right now if you set a the Content-Type header in the request and you leave the body of the request empty angular2 is throwing 'ORIGINAL EXCEPTION: TypeError: Cannot read property 'toString' of null' before even try to make the request.</p>
<p dir="auto"><strong>Expected/desired behavior</strong><br>
As far as I know if you have an Content-Type header and an empty request body it is a perfectly valid request. I suppose the correct behaviour is to execute the request.</p>
<p dir="auto"><strong>Reproduction of the problem</strong><br>
You can see the wrong behaviour in this plnkr.<br>
<a href="https://plnkr.co/edit/9J1hTVC8W65vLTU3ByhO?p=preview" rel="nofollow">https://plnkr.co/edit/9J1hTVC8W65vLTU3ByhO?p=preview</a></p>
<p dir="auto"><strong>What is the expected behavior?</strong><br>
I expect to be able to load the application if I made a request with Content-Type and without a body with angular2 http module</p>
<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong><br>
I think it is perfectly valid http request and don't see any value in make them impossible with angular2 http library</p>
<p dir="auto"><strong>Please tell us about your environment:</strong></p>
<ul dir="auto">
<li><strong>Angular version:</strong> 2.0.0-rc.5</li>
<li><strong>Browser:</strong> [all]<br>
I have tried with chrome/firefox/safari.</li>
<li><strong>Language:</strong> [TypeScript]<br>
I have just used what plnkr provides for their default angular2 typescript plunk.</li>
</ul>