This looks like an issue with new whiteboard implementation and way SlingMainServlet gets registered. Opened SLING-6089 for this Chetan Mehrotra
On Thu, Sep 29, 2016 at 8:23 PM, Bertrand Delacretaz <[email protected]> wrote: > Hi (Chetan mostly I suppose), > > I played with the Sling Tracer snapshot installed in the current trunk > launchpad, and it looks like the requests that hit the > SlingMainServlet are not recorded, am I doing something wrong? > > In the example below, the second response doesn't have a > Sling-Tracer-Request-Id header. > > -Bertrand > > $ curl -u admin:admin -D - -H "Sling-Tracer-Record:true" > "http://localhost:8080/system/console?trace=oak-writes"; > HTTP/1.1 302 Found > Date: Thu, 29 Sep 2016 14:49:15 GMT > Sling-Tracer-Request-Id: f5de031a-093a-4803-a8ce-630fdb63e554 > Sling-Tracer-Protocol-Version: 1 > Location: http://localhost:8080/system/console/bundles > Content-Length: 0 > > $ curl -u admin:admin -D - -H "Sling-Tracer-Record:true" > "http://localhost:8080/.json?trace=oak-writes"; > HTTP/1.1 200 OK > Date: Thu, 29 Sep 2016 14:49:18 GMT > X-Content-Type-Options: nosniff > X-Frame-Options: SAMEORIGIN > Content-Type: application/json;charset=utf-8 > Content-Length: 141 > > {"jcr:primaryType":"rep:root","jcr:mixinTypes...
