@5idu opened this Issue on February 17th 2022

Expected Behavior

options request should not recorded!

Current Behavior

options request will also be recorded

Possible Solution

The server should filter out the options request and not participate in the record.

Steps to Reproduce (for Bugs)



Your Environment

  • Matomo Version: 4.7.1
  • MySQL version: 10.6.5-MariaDB-1:10.6.5+maria~focal
  • PHP Version: 8.0.15
  • Server Operating System: centos7
  • Additionally installed plugins:
  • Browser: chrome98
  • Operating System: macos 12.1
@5idu commented on February 18th 2022

@tsteur Hi, are you sure this is a bug? and will be fixed in the next version?

@tsteur commented on February 18th 2022 Member

@5idu I haven't looked into this yet but put it for now into Matomo 5 to consider changing this there. This release could be 6-12 months away as we don't have specific plans for a Matomo 5 release yet. We probably wouldn't want to change anything there earlier just in case it would cause any kind of regressions where people rely on this working for some reason.

@5idu commented on February 18th 2022

@tsteur Thanks Reply. looking forward to your verification result.
Now my solution is to intercept the options request on nginx, and then the statistical results are normal.

@tsteur commented on February 18th 2022 Member

@5idu do you know what issues these OPTIONS requests in the first place?

@5idu commented on February 18th 2022

@tsteur since cross-domain, browser client send the options request, this is fine.
However, after the options request is sent to the matomo server, matomo will still process the data passed by the options request, resulting in repeated statistics.

@tsteur commented on February 18th 2022 Member

Thanks for this, that's really helpful. I will move this in the 4.9 milestone so we look into this earlier. If someone in the team could reproduce this that be great.

@peterhashair commented on March 29th 2022 Contributor

Haven't reproduced this locally, but this could be caused by CORS preflight, I guess we could filter those request types, stop them for the double record.

This Issue was closed on April 11th 2022
Powered by GitHub Issue Mirror