[nginx] Adding Support for Weak ETags

[Adam Arsenault]

Hi Maxim/Aaron,

Would love to see support for Weak Etags in nginx. The lack of support for
gzip + etags has been a major problem for us as we use etags for caching
(and need gzip to work with it) in a bunch of different place in our
application.

Let me know if there is anything I can do to help out here as well.

Thanks,
Adam Arsenault


On Tue, Apr 29, 2014 at 11:47 AM, Aaron Peschel <aaron.peschel at gmail.com>wrote:

> Hello Maxim,
>
> If you provide a copy of your newer draft patch, I am willing to spend
> time helping improve it as you see fit.
>
> -Aaron Peschel
>
> On Fri, Apr 25, 2014 at 4:35 AM, Maxim Dounin <mdounin at mdounin.ru> wrote:
> > Hello!
> >
> > On Thu, Apr 24, 2014 at 06:20:24PM -0700, Aaron Peschel wrote:
> >
> >> Hi Maxim,
> >>
> >> Is the draft patch the same as the one that your posted in the
> >> previous thread, or has more work been done since then?
> >
> > The one I've posted is to ignore weak etags.  The draft one is to
> > downgrade strict etags to weak etags.
> >
> >>
> >> -Aaron Peschel
> >>
> >> On Mon, Apr 21, 2014 at 5:26 AM, Maxim Dounin <mdounin at mdounin.ru>
> wrote:
> >> > Hello!
> >> >
> >> > On Thu, Apr 17, 2014 at 05:39:40PM -0700, Aaron Peschel wrote:
> >> >
> >> >> Hello,
> >> >>
> >> >> I am interested in getting support for Weak ETags into the mainline.
> >> >> There was some discussion previously in here previously that
> developed
> >> >> a quick patch to add support. What additional functionality would be
> >> >> required and what steps should be followed to get weak etag
> >> >> functionality added to nginx? I am willing to do the work, I just
> need
> >> >> some help with heading in the right direction.
> >> >
> >> > I had a quick draft patch sitting in my patchqueue since previous
> >> > discussion (see [1]) to downgrade strict etags to weak ones.  It
> >> > needs more work though, as I'm not yet happy with the code.  I
> >> > hope I'll be able to find some time and finish it in 1.7.x.
> >> >
> >> > [1]
> http://mailman.nginx.org/pipermail/nginx-devel/2013-November/004523.html
> >> >
> >> > --
> >> > Maxim Dounin
> >> > http://nginx.org/
> >> >
> >> > _______________________________________________
> >> > nginx-devel mailing list
> >> > nginx-devel at nginx.org
> >> > http://mailman.nginx.org/mailman/listinfo/nginx-devel
> >>
> >> _______________________________________________
> >> nginx-devel mailing list
> >> nginx-devel at nginx.org
> >> http://mailman.nginx.org/mailman/listinfo/nginx-devel
> >
> > --
> > Maxim Dounin
> > http://nginx.org/
> >
> > _______________________________________________
> > nginx-devel mailing list
> > nginx-devel at nginx.org
> > http://mailman.nginx.org/mailman/listinfo/nginx-devel
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
>



-- 
[image: HootSuite]

*Adam Arsenault*
Senior Software Engineer, Mobile Web  |  HootSuite
@Adam_Arsenault <http://twitter.com/Adam_Arsenault> |
hootsuite<http://www.hootsuite.com/>
 | blog <http://blog.hootsuite.com/> | facebook<http://facebook.com/hootsuite>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20140429/c579f359/attachment.html>