<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>31200</bug_id>
          
          <creation_ts>2009-11-06 00:28:07 -0800</creation_ts>
          <short_desc>Tests in http/tests/security/mixedContent start to fail when new tests are added</short_desc>
          <delta_ts>2009-11-11 14:09:33 -0800</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>Layout and Rendering</component>
          <version>528+ (Nightly build)</version>
          <rep_platform>Mac</rep_platform>
          <op_sys>OS X 10.5</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          <blocked>29972</blocked>
    
    <blocked>31301</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Roland Steiner">rolandsteiner</reporter>
          <assigned_to name="Mark Rowe (bdash)">mrowe</assigned_to>
          <cc>abarth</cc>
    
    <cc>ap</cc>
    
    <cc>bdakin</cc>
    
    <cc>beidson</cc>
    
    <cc>darin</cc>
    
    <cc>eric</cc>
    
    <cc>mrowe</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>161102</commentid>
    <comment_count>0</comment_count>
    <who name="Roland Steiner">rolandsteiner</who>
    <bug_when>2009-11-06 00:28:07 -0800</bug_when>
    <thetext>Discovered in r50495: when adding layout tests to the test set, http/tests/security/mixedContent/about-blank-iframe-in-main-frame.html fails as it has additional frame load delegate callbacks in the output.

To reproduce (as of writing this bug report): add more than 12 layout tests to the test set that run before http/tests/security/mixedContent/about-blank-iframe-in-main-frame.html (i.e., are before it in lexical order). Apart from the tests in fast/ruby that initially caused this, it also reproduced when duplicating fast/lists, fast/clip or fast/block/basic.

Tested on 2 different Mac Pros (only seems to occur on Mac).

[CC&apos;ing abarth, ap, brady, as discussed with bdash on IRC]</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>161103</commentid>
    <comment_count>1</comment_count>
    <who name="Roland Steiner">rolandsteiner</who>
    <bug_when>2009-11-06 00:43:22 -0800</bug_when>
    <thetext>Correction:</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>161110</commentid>
    <comment_count>2</comment_count>
    <who name="Roland Steiner">rolandsteiner</who>
    <bug_when>2009-11-06 01:40:48 -0800</bug_when>
    <thetext>[Sorry about the comment spam, didn&apos;t mean to commit the previous one yet]

Corrections and additions after even more testing: 

Actually different tests in http/tests/security/mixedContent start to fail, not just about-blank-iframe-in-main-frame.html.

However, it&apos;s only ever 1 test that fails, and which test fails seems to be consistent for a given set of added tests.

Furthermore, if you remove 1 test from the added test set, the next test in line in http/tests/security/mixedContent fails. It therefore seems this is caused strictly by the number of tests (rather than any content) that come before.

And to even further add to the fun: if you add a LOT of layout tests (e.g., duplicating fast/block and fast/clip), everything runs through fine again.

This leads me to believe that perhaps something in http/tests/security/mixedContent is sensitive to some sort of run-over of the layout count. I.e., a test in this directory fails if it happens to be exactly the, say, 1000th test.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162253</commentid>
    <comment_count>3</comment_count>
    <who name="Beth Dakin">bdakin</who>
    <bug_when>2009-11-10 15:32:49 -0800</bug_when>
    <thetext>The bot is officially red because of this issue now. I added new tests for a new feature, and this bug is officially exposed. We should try to find a quick resolution to avoid a red bot.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162261</commentid>
    <comment_count>4</comment_count>
    <who name="Adam Barth">abarth</who>
    <bug_when>2009-11-10 15:56:56 -0800</bug_when>
    <thetext>(In reply to comment #3)
&gt; The bot is officially red because of this issue now. I added new tests for a
&gt; new feature, and this bug is officially exposed. We should try to find a quick
&gt; resolution to avoid a red bot.

Huh?  Why is it ok for you to land a patch that turns the tree red?  It seems fixing this bug is a re-requisite for landing that patch.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162264</commentid>
    <comment_count>5</comment_count>
    <who name="Mark Rowe (bdash)">mrowe</who>
    <bug_when>2009-11-10 15:58:18 -0800</bug_when>
    <thetext>(In reply to comment #4)
&gt; (In reply to comment #3)
&gt; &gt; The bot is officially red because of this issue now. I added new tests for a
&gt; &gt; new feature, and this bug is officially exposed. We should try to find a quick
&gt; &gt; resolution to avoid a red bot.
&gt; 
&gt; Huh?  Why is it ok for you to land a patch that turns the tree red?  It seems
&gt; fixing this bug is a re-requisite for landing that patch.

Presumably because she didn’t realize that would happen.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162266</commentid>
    <comment_count>6</comment_count>
    <who name="Beth Dakin">bdakin</who>
    <bug_when>2009-11-10 16:02:04 -0800</bug_when>
    <thetext>(In reply to comment #5)
&gt; (In reply to comment #4)
&gt; &gt; (In reply to comment #3)
&gt; &gt; &gt; The bot is officially red because of this issue now. I added new tests for a
&gt; &gt; &gt; new feature, and this bug is officially exposed. We should try to find a quick
&gt; &gt; &gt; resolution to avoid a red bot.
&gt; &gt; 
&gt; &gt; Huh?  Why is it ok for you to land a patch that turns the tree red?  It seems
&gt; &gt; fixing this bug is a re-requisite for landing that patch.
&gt; 
&gt; Presumably because she didn’t realize that would happen.

Indeed I did not. Also, we can not have a bug that blocks adding new tests. That&apos;s insane.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162268</commentid>
    <comment_count>7</comment_count>
    <who name="Eric Seidel (no email)">eric</who>
    <bug_when>2009-11-10 16:02:21 -0800</bug_when>
    <thetext>*** Bug 31305 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162270</commentid>
    <comment_count>8</comment_count>
    <who name="Eric Seidel (no email)">eric</who>
    <bug_when>2009-11-10 16:04:08 -0800</bug_when>
    <thetext>It&apos;s also blocking two patches in the commit queue, see bug 31305. :)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162292</commentid>
    <comment_count>9</comment_count>
    <who name="Mark Rowe (bdash)">mrowe</who>
    <bug_when>2009-11-10 17:00:22 -0800</bug_when>
    <thetext>Printing out the error reveals:

main frame - didFailProvisionalLoadWithError Error Domain=NSURLErrorDomain Code=-1202 UserInfo=0x10269f380 &quot;The certificate for this server is invalid. You might be connecting to a server that is pretending to be “127.0.0.1” which could put your confidential information at risk.&quot; Underlying Error=(Error Domain=kCFErrorDomainCFNetwork Code=-1202 UserInfo=0x1026d3400 &quot;The certificate for this server is invalid. You might be connecting to a server that is pretending to be “127.0.0.1” which could put your confidential information at risk.&quot;)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162298</commentid>
    <comment_count>10</comment_count>
    <who name="Mark Rowe (bdash)">mrowe</who>
    <bug_when>2009-11-10 17:04:57 -0800</bug_when>
    <thetext>Ok, this is trivial to reproduce:

run-webkit-tests --nthly=1 http/tests/security/mixedContent

Every test fails in this manner.  If you instead did:

run-webkit-tests --nthly=2 http/tests/security/mixedContent

you&apos;d see an interesting pattern where every second test fails in the same way.

This makes the problem relatively obvious: the first test in a given instance of DRT to use HTTPS gets extra frame load callbacks as a result of the self-signed SSL certificate.  It tells the network layer to ignore the certificate errors and then retry.  The new tests had the effect of shifting the point at which DRT was restarted, exposing this issue.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162300</commentid>
    <comment_count>11</comment_count>
    <who name="Mark Rowe (bdash)">mrowe</who>
    <bug_when>2009-11-10 17:15:10 -0800</bug_when>
    <thetext>I have a fix for this.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162302</commentid>
    <comment_count>12</comment_count>
    <who name="Mark Rowe (bdash)">mrowe</who>
    <bug_when>2009-11-10 17:29:50 -0800</bug_when>
    <thetext>Fixed in r50783.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162665</commentid>
    <comment_count>13</comment_count>
      <attachid>42997</attachid>
    <who name="Alexey Proskuryakov">ap</who>
    <bug_when>2009-11-11 13:56:53 -0800</bug_when>
    <thetext>Created attachment 42997
follow-up fix for Tiger

One patch per bug!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162666</commentid>
    <comment_count>14</comment_count>
      <attachid>42997</attachid>
    <who name="Darin Adler">darin</who>
    <bug_when>2009-11-11 13:58:42 -0800</bug_when>
    <thetext>Comment on attachment 42997
follow-up fix for Tiger

&gt; +#if BUILDING_ON_TIGER
&gt; +	// Initialize internal NSuRLRequest data for setAllowsAnyHTTPSCertificate:forHost: to work properly.
&gt; +	[[[[NSURLRequest alloc] init] autorelease] HTTPMethod];
&gt; +#endif

Bad spelling of NSURLRequest. Comment should use the phrase &quot;work around for Tiger bug&quot;, I think.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162668</commentid>
    <comment_count>15</comment_count>
      <attachid>42997</attachid>
    <who name="Mark Rowe (bdash)">mrowe</who>
    <bug_when>2009-11-11 13:59:13 -0800</bug_when>
    <thetext>Comment on attachment 42997
follow-up fix for Tiger

&gt; Index: WebKitTools/DumpRenderTree/mac/DumpRenderTree.mm
&gt; ===================================================================
&gt; --- WebKitTools/DumpRenderTree/mac/DumpRenderTree.mm	(revision 50817)
&gt; +++ WebKitTools/DumpRenderTree/mac/DumpRenderTree.mm	(working copy)
&gt; @@ -604,6 +604,10 @@ void dumpRenderTree(int argc, const char
&gt;  
&gt;      // &lt;http://webkit.org/b/31200&gt; In order to prevent extra frame load delegate logging being generated if the first test to use SSL
&gt;      // is set to log frame load delegate calls we ignore SSL certificate errors on localhost and 127.0.0.1.
&gt; +#if BUILDING_ON_TIGER
&gt; +	// Initialize internal NSuRLRequest data for setAllowsAnyHTTPSCertificate:forHost: to work properly.
&gt; +	[[[[NSURLRequest alloc] init] autorelease] HTTPMethod];
&gt; +#endif

You appear to have inserted some tabs here!  And you’re missing an uppercase U in NSURLRequest.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>162674</commentid>
    <comment_count>16</comment_count>
    <who name="Alexey Proskuryakov">ap</who>
    <bug_when>2009-11-11 14:09:33 -0800</bug_when>
    <thetext>&gt; Comment should use the phrase &quot;work around for
&gt; Tiger bug&quot;, I think.

It&apos;s not an API, so while I&apos;m not sure that its behavior on Tiger was formally a bug. But OK.

Committed r50842</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>42997</attachid>
            <date>2009-11-11 13:56:53 -0800</date>
            <delta_ts>2009-11-11 13:59:13 -0800</delta_ts>
            <desc>follow-up fix for Tiger</desc>
            <filename>TigerSSL.txt</filename>
            <type>text/plain</type>
            <size>1578</size>
            <attacher name="Alexey Proskuryakov">ap</attacher>
            
              <data encoding="base64">SW5kZXg6IFdlYktpdFRvb2xzL0NoYW5nZUxvZwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSBXZWJLaXRUb29scy9D
aGFuZ2VMb2cJKHJldmlzaW9uIDUwODE3KQorKysgV2ViS2l0VG9vbHMvQ2hhbmdlTG9nCSh3b3Jr
aW5nIGNvcHkpCkBAIC0xLDMgKzEsMTMgQEAKKzIwMDktMTEtMTEgIEFsZXhleSBQcm9za3VyeWFr
b3YgIDxhcEBhcHBsZS5jb20+CisKKyAgICAgICAgUmV2aWV3ZWQgYnkgTk9CT0RZIChPT1BTISku
CisKKyAgICAgICAgaHR0cHM6Ly9idWdzLndlYmtpdC5vcmcvc2hvd19idWcuY2dpP2lkPTMxMjAw
CisgICAgICAgIFRlc3RzIGluIGh0dHAvdGVzdHMvc2VjdXJpdHkvbWl4ZWRDb250ZW50IHN0YXJ0
IHRvIGZhaWwgd2hlbiBuZXcgdGVzdHMgYXJlIGFkZGVkCisKKyAgICAgICAgKiBEdW1wUmVuZGVy
VHJlZS9tYWMvRHVtcFJlbmRlclRyZWUubW06IChkdW1wUmVuZGVyVHJlZSk6IE1hZ2ljYWxseSBt
YWtlIHRoZSB3b3JrYXJvdW5kCisgICAgICAgIHdvcmsgb24gVGlnZXIsIHRvby4KKwogMjAwOS0x
MS0xMSAgS2VubmV0aCBSb2hkZSBDaHJpc3RpYW5zZW4gIDxrZW5uZXRoQHdlYmtpdC5vcmc+CiAK
ICAgICAgICAgUmV2aWV3ZWQgYnkgU2ltb24gSGF1c21hbm4uCkluZGV4OiBXZWJLaXRUb29scy9E
dW1wUmVuZGVyVHJlZS9tYWMvRHVtcFJlbmRlclRyZWUubW0KPT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gV2ViS2l0
VG9vbHMvRHVtcFJlbmRlclRyZWUvbWFjL0R1bXBSZW5kZXJUcmVlLm1tCShyZXZpc2lvbiA1MDgx
NykKKysrIFdlYktpdFRvb2xzL0R1bXBSZW5kZXJUcmVlL21hYy9EdW1wUmVuZGVyVHJlZS5tbQko
d29ya2luZyBjb3B5KQpAQCAtNjA0LDYgKzYwNCwxMCBAQCB2b2lkIGR1bXBSZW5kZXJUcmVlKGlu
dCBhcmdjLCBjb25zdCBjaGFyCiAKICAgICAvLyA8aHR0cDovL3dlYmtpdC5vcmcvYi8zMTIwMD4g
SW4gb3JkZXIgdG8gcHJldmVudCBleHRyYSBmcmFtZSBsb2FkIGRlbGVnYXRlIGxvZ2dpbmcgYmVp
bmcgZ2VuZXJhdGVkIGlmIHRoZSBmaXJzdCB0ZXN0IHRvIHVzZSBTU0wKICAgICAvLyBpcyBzZXQg
dG8gbG9nIGZyYW1lIGxvYWQgZGVsZWdhdGUgY2FsbHMgd2UgaWdub3JlIFNTTCBjZXJ0aWZpY2F0
ZSBlcnJvcnMgb24gbG9jYWxob3N0IGFuZCAxMjcuMC4wLjEuCisjaWYgQlVJTERJTkdfT05fVElH
RVIKKwkvLyBJbml0aWFsaXplIGludGVybmFsIE5TdVJMUmVxdWVzdCBkYXRhIGZvciBzZXRBbGxv
d3NBbnlIVFRQU0NlcnRpZmljYXRlOmZvckhvc3Q6IHRvIHdvcmsgcHJvcGVybHkuCisJW1tbW05T
VVJMUmVxdWVzdCBhbGxvY10gaW5pdF0gYXV0b3JlbGVhc2VdIEhUVFBNZXRob2RdOworI2VuZGlm
CiAgICAgW05TVVJMUmVxdWVzdCBzZXRBbGxvd3NBbnlIVFRQU0NlcnRpZmljYXRlOllFUyBmb3JI
b3N0OkAibG9jYWxob3N0Il07CiAgICAgW05TVVJMUmVxdWVzdCBzZXRBbGxvd3NBbnlIVFRQU0Nl
cnRpZmljYXRlOllFUyBmb3JIb3N0OkAiMTI3LjAuMC4xIl07CiAK
</data>
<flag name="review"
          id="24652"
          type_id="1"
          status="+"
          setter="darin"
    />
          </attachment>
      

    </bug>

</bugzilla>