<html>
    <head>
      <base href="https://bugs.webkit.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Web Inspector: Resource names should be less ambiguous"
   href="https://bugs.webkit.org/show_bug.cgi?id=176765">176765</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Web Inspector: Resource names should be less ambiguous
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>WebKit
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>WebKit Nightly Build
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>Normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P2
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>Web Inspector
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>webkit-unassigned@lists.webkit.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>joepeck@webkit.org
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>inspector-bugzilla-changes@group.apple.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Resource names should be less ambiguous

Example 1: Query string differences

    If a page loads:

        data.json?t=1
        data.json?t=2
        data.json?t=3

    Each of these show up as:

        data.json
        data.json
        data.json

    would be nicer:

        data.json?t=1
        data.json?t=2
        data.json?t=3


Example 2: Ambiguous last path component

Can happen with REST endpoints:
<a href="https://twitter.com/Skyrpex/status/905450335799570432">https://twitter.com/Skyrpex/status/905450335799570432</a>

    If a page loads:

        /api/user/913578
        /api/group/78425
        /api/comment/124123

    Each of these show up as:

        913578
        78425
        124123

    Would be nicer:

        user/913578
        group/78425
        comment/124123</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>