launchpadlib attempts to use TE (which does not work well in our environment)
Bug #574697 reported by
Leonard Richardson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
launchpadlib |
Triaged
|
High
|
Unassigned |
Bug Description
launchpadlib sends the TE header to indicate that it would like compressed versions of resources. If the TE header is present, lazr.restful will process it correctly. But launchpad is not directly connected to clients, because there are intermediaries present, so TE compression cannot be used without the intermediaries all being aware back into the datacentre (and to our outer most intermediary which would have to do the compression).
CE is much simpler and more robust, we should use it. This requires WADL serving to be simplified (removed from the appservers, so that the apache stack, which will do the just-in-time CE for us, handles ETag validation).
Changed in launchpad-foundations: | |
status: | New → Triaged |
importance: | Undecided → High |
summary: |
- launchpadlib attempts to use TE + launchpadlib attempts to use TE (which does not work well in our + environment) |
tags: | added: easy |
To post a comment you must log in.
As an experiment, I told launchpadlib to include a 'Foo-Bar' header. This showed up in the appropriate place as HTTP_FOO_BAR. Something seems to be specifically stripping off the TE header. Apache?