Ticket #1152 (new)

Opened 6 years ago

Last modified 4 years ago

Support nodewatcher output compression

Reported by: kostko Owned by: kostko
Priority: normal Milestone: Next milestone
Component: nodewatcher/agent Version:
Keywords: Cc:
Related nodes: Realization state:
Blocking: Effort: normal
Blocked by: Security sensitive: no


Since the nodewatcher output can get quite big, we should support gzip compression of it. We can simply put any generated data through gzip and output this to the browser. For backwards compatibility, compression would only be enabled when specified in the arguments like ?compress=gzip.

Change History

comment:1 Changed 6 years ago by mitar

Why not do content negotiation? If the client says in the HTTP headers that it supports gzip, then we do gzip?

comment:2 Changed 6 years ago by kostko

Yes, that is even better.

comment:3 Changed 5 years ago by kostko

This has now changed as we no longer use the old reporting cgi-bin scripts, but instead use nodewatcher-agent which preprocesses and caches the data. It could always output gzip-compressed files and the parser would always decompress them.

The most elegant way of course would be for uhttpd to support gzip, but if we want that we will have to implement it ourselves:

comment:4 Changed 4 years ago by mitar

  • Milestone changed from 3.0b to Next milestone

Let's do this later.

Note: See TracTickets for help on using tickets.