# If-Modified-Since to upstream servers

**URL:** <https://www.ruby-forum.com/t/if-modified-since-to-upstream-servers/223346>\
**Category:** NGINX\
**Created:** [October 1, 2012, 8:52am UTC](https://www.ruby-forum.com/t/if-modified-since-to-upstream-servers/223346 "2012-10-01T08:52:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![aris](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/258eb7/32.png) [@aris](https://www.ruby-forum.com/u/aris)\
**Post date:** [October 1, 2012, 8:52am UTC](https://www.ruby-forum.com/t/if-modified-since-to-upstream-servers/223346/1 "2012-10-01T08:52:51Z")

</div>

Hi.

I’d like to know status of “1.3 Planned If-Modified-Since to upstream  
servers”.

Thank you.

–  
shin fukuda [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![shin\_fukuda](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ecc23a/32.png) [@shin\_fukuda](https://www.ruby-forum.com/u/shin_fukuda)\
**Post date:** [October 3, 2012, 12:10pm UTC](https://www.ruby-forum.com/t/if-modified-since-to-upstream-servers/223346/2 "2012-10-03T12:10:48Z")

</div>

Probably to appear around Jan 2013, maybe sooner

---

<div class="post-metadata">

**Author:** ![shin\_fukuda](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ecc23a/32.png) [@shin\_fukuda](https://www.ruby-forum.com/u/shin_fukuda)\
**Post date:** [October 5, 2012, 3:11am UTC](https://www.ruby-forum.com/t/if-modified-since-to-upstream-servers/223346/3 "2012-10-05T03:11:50Z")

</div>

Hi.

That’s good news!

On Wed, 3 Oct 2012 14:10:26 +0400  
Andrew A. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > 
> 
> nginx mailing list  
> [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
> [mailman.nginx.org archive](http://mailman.nginx.org/mailman/listinfo/nginx)

–  
shin fukuda [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)
