Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #18954

Closed (moved)
(moved)
Open
Created May 03, 2016 by Georg Koppen@gk

Trac should not make request to next/related bug

Suppose you are not logged into our Trac bugtracker and have your browser console open while loading #18915 (moved). At the very end you'll oddly see that the follow-up bug #18916 (closed) get requested, too. There is nothing special about this bug. This happens for any bug as far as I can see and Trac should not doing this because I only requested #18915 (moved).

It gets weirder as soon as I am logged in because then the second bug requested is not the one with the following bug number but one that seems related to my activity. Collecting this information seems already a bit overreaching to me but even if we do this for some reason this information should never go over the network (while I am using Trac).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking