[Bug 4134] New: Mercurial v.2.8.1 - HTTP Error: 404 (Not Found) - Issue

[mercurial-bugs at selenic.com]

http://bz.selenic.com/show_bug.cgi?id=4134

          Priority: normal
            Bug ID: 4134
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Mercurial v.2.8.1 - HTTP Error: 404 (Not Found) -
                    Issue
          Severity: bug
    Classification: Unclassified
                OS: Windows
          Reporter: philip.w.mcadams at intel.com
          Hardware: PC
            Status: UNCONFIRMED
           Version: 2.8.1
         Component: Mercurial
           Product: Mercurial

Mercurial Team,

I’ve upgraded our Mercurial Development Server (and my laptop) to Mercurial
2.8.1 and when testing pushing our Trunk to a development sandbox I received
error HTTP Error: 404 (Not Found).  This was the  similar to the issue we’d
found when we upgraded to Mercurial 2.5.4 and found the Open SSL workaround to
resolve the issue. From there I tested smaller repos to see if repo size was an
issue.

Testing Conducted

1.       Our main Trunk Test: At the final phase of the push 250462 kb of data
stops at around 121,000kb and errors out with HTTP Error: 404 (Not Found).  Our
main Trunk’s Size is at 162 MB.

2.       Medium Size Test: Tested creating a Medium sized sandbox as well and
also hit HTTP Error: 404 (Not Found) at a certain point in the push.  Medium
size test was 68 MB.

3.       Small Repo: Lastly I tested a basically empty repo (176 bytes) and was
able to push fine and create a sandbox.

When I’d previously tested Mercurial 2.7.2 I did not run into any of the issues
as were found with this release.  

In reviewing the 2.8 release notes there is a mention of using ui.tls=False to
allow SSLv2 or SSLv3 connections as shown below:


Could the SSL configuration changes be causing the issue with larger pushes?

Can you provide some guidance on where the “ui.tls=False” info should be added?
Hgweb.config file?

Matt encouraged me to enter this info I'd initially sent as an email as a bug
in your tracker. The question I have is this truly a bug or simply an issue
related to the configuration of SSL on our server per the requirements of
Mercurial v.2.8.1.

Thank you.

Philip McAdams
Systems Administrator - NVM Solutions Group Systems Engineering Apps &
Infrastructure
Desk: (916) 377-6156 Cell: (916) 534-0092 Pole: FM3-1-D7

-- 
You are receiving this mail because:
You are on the CC list for the bug.