DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42730>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42730

           Summary: first GET message length greater than 166 bytes fails
                    from IPv6
           Product: Apache httpd-2
           Version: 2.2.3
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P4
         Component: mod_negotiation
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]
                CC: [EMAIL PROTECTED]


Using Fedora 7 I was unable to connect to l4x.org using its IPv6 address from
Firefox 2.0.0.4-2.  Disabling IPv6 support in Firefox let me connect, and I can
connect to myself running Apache 2.2.4 using IPv6.  I was able to connect to
l4x.org's IPv6 IP address using curl.  By adding headers in curl I found that if
the length of the first GET command is greater than 166 bytes nothing is 
returned.
This command succeeds:

curl --header "Accept:" --header "Accept-123456:e" --header "Accept-23:u" 
l4x.org

whereas this one fails:

curl --header "Accept:" --header "Accept-123456:e" --header "Accept-234:u" 
l4x.org

Wireshark shows that the initial 3-way handshake works, but l4x.org responds to
the long GET command by repeating its [SYN,ACK], as though it had received
nothing.  The client re-transmits with no effect.

Other clients I tested are Konqueor, Epiphany, Kazehakase and Opera, all of
which failed, and dillo, which succeeded, though dillo-i18n failed.

I have only one computer, and no personal access to another that has IPv6
connectivity, so my testing is limited to finding web hosts with IPv6
connectivity and seeing if they work.  I do not know of any web hosts with IPv6
connectivity running Apache 2.2.4.  

I was reluctant to report this problem because it seems so obvious that it
should have been fixed long ago.  I decided that I would rather risk wasting
someone's time than risk having the bug go unreported.  If this is actually a
problem in my computer, router or ISP, please let me know.  My router runs
dd-wrt with IPv6 enabled and by ISP is Comcast.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to