Bug 707816 - anyterm cannot be used with nginx or lighttpd relay modules.
Summary: anyterm cannot be used with nginx or lighttpd relay modules.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anyterm
Version: 15
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
Assignee: Alexander Boström
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-26 03:32 UTC by Jeff Johnson
Modified: 2012-08-07 14:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 14:35:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Patch sourced from http://bugs.gentoo.org/attachment.cgi?id=218291&action=diff&context=patch&collapsed=&headers=1&format=raw and known to work with the SRPM locally. (1.79 KB, patch)
2011-05-26 03:32 UTC, Jeff Johnson
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Gentoo 303339 0 None None None Never

Description Jeff Johnson 2011-05-26 03:32:23 UTC
Created attachment 500976 [details]
Patch sourced from http://bugs.gentoo.org/attachment.cgi?id=218291&action=diff&context=patch&collapsed=&headers=1&format=raw and known to work with the SRPM locally.

Description of problem:
(Lifted from the Gentoo bugzilla, not my original report, but accurately describes the issues):

As by version 1.1.29 anyterm doesn't honor HTTP/1.0 client requests
and will spam them with chunked responses.

This results in incompatibility with both lighttpd and nginx
since both expect a HTTP/1.0 compatible response.

With the attached patch the missing support is added and anyterm can
be used on the above servers (via mod_proxy) as well as non-HTTP/1.1 clients.

Reproducible: Always

Steps to Reproduce:
1. emerge anyterm with the default configuration (localhost, port 7676)
2. setup lighttpd or nginx to proxy request to the above host:port
3. try to open the proxied anyterm in your browser

Actual Results:  
lighttpd:  displays a plain '0'
nginx: displays part of the response header + '0'

Expected Results:  
A usable anyterm window should appear.

Comment 1 Alexander Boström 2011-06-07 10:39:11 UTC
You should bring this up in the Anyterm forum. Post the patch and description there so that phil can take a look at it and we'll see what happens. (Post the URL for the thread here.)

http://anyterm.org/forums/viewforum.php?id=2

Comment 2 Fedora Admin XMLRPC Client 2011-07-22 12:40:48 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2012-08-07 14:35:29 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.