Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-3840

Investigate: Why does MacOS IGB request updates.xml twice?

    Details

    • Type: Task
    • Status: To-Do (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      To track usage, we configured bioviz.org to log requests for updates.xml - see: IGBF-3568.

      After implementing and deploying the new logging mechanism, AL checked the log.

      The log revealed that when IGB starts, it sends two requests for updates.xml, with two different user-agent strings.

      For this task, find out where in the IGB code these two requests are being made, and why MacOS and Windows user-agents are reported.

      Here are the relevant lines in the log:

      16.98.114.149 - - [04/Aug/2024:23:38:48 +0000] "GET /igb/releases/current/updates.xml HTTP/1.1" 200 7410 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64)"
      16.98.114.149 - - [04/Aug/2024:23:38:51 +0000] "GET /igb/releases/current/updates.xml HTTP/1.1" 200 1692 "-" "IGB/10.1.0; Mac OS X/14.3 (aarch64); en_US; Java/21.0.2"

        Attachments

          Activity

          Hide
          ann.loraine Ann Loraine added a comment - - edited

          I suspect the reason for the double-access with different user agent strings is that the updating code, which comes from the installer, is responsible.
          We can check to see if IGB does a similar thing with other HTTP requests.
          Fore example, we are hosting default Quickloads on BioViz.org and so, when IGB starts, reaches out for that file. For example, here's a recent log entry:

          99.69.51.247 - - [19/Dec/2025:15:13:14 +0000] "GET /quickload/genome-in-a-bottle/contents.txt HTTP/1.1" 200 465 "-" "IGB/10.0.1; Mac OS X/15.7.2 (aarch64); en_US; Java/21.0.2"
          
          Show
          ann.loraine Ann Loraine added a comment - - edited I suspect the reason for the double-access with different user agent strings is that the updating code, which comes from the installer, is responsible. We can check to see if IGB does a similar thing with other HTTP requests. Fore example, we are hosting default Quickloads on BioViz.org and so, when IGB starts, reaches out for that file. For example, here's a recent log entry: 99.69.51.247 - - [19/Dec/2025:15:13:14 +0000] "GET /quickload/genome-in-a-bottle/contents.txt HTTP/1.1" 200 465 "-" "IGB/10.0.1; Mac OS X/15.7.2 (aarch64); en_US; Java/21.0.2"

            People

            • Assignee:
              Unassigned
              Reporter:
              ann.loraine Ann Loraine
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: