Skip to content

DEPRECATED Get MPG data for from website

Alix Lourme edited this page Aug 3, 2021 · 1 revision

Some bugs troubleshooting would require MPG data ; the content of HTTP requests received (GET requests) or sent (POST requests) from/to MPG website:

  • home : GET /user/dashboard
  • coach: GET /league/[yourLeagueId]/coach
  • transfer : GET /league/[yourLeagueId]/transfer/buy
  • team update : POST /league/[yourLeagueId]/coach

To catch them, you should use the network debug tool of your internet brower. It is accessible via the F12 key (Details : Firefox / Chrome / Edge).

Activate browser network monitor

Sample with FireFox and GET /league/[yourLeagueId]/coach page.

Connect on MPG website, active the debug mode with F12 and:

  1. Select monitor network
  2. Click on MPG feature

Catch GET content

Process to use for:

  • home : GET /user/dashboard
  • coach: GET /league/[yourLeagueId]/coach
  • transfer : GET /league/[yourLeagueId]/transfer/buy

When feature click done, the requests will be displayed in the network monitor:

  1. Find the wanted request and click on it
  2. Click on Reponse tab on the right of debug tool
  3. At the bottom of page, copy/paste the brut content of response request

Add this content in bug description, using file upload or code block.

Catch POST content

Process to use for:

  • team update : POST /league/[yourLeagueId]/coach

When feature click done, the requests will be displayed in the network monitor:

  1. Find the wanted request and click on it
  2. Click on Parameters tab on the right of debug tool
  3. At the bottom of page, copy/paste the brut content of parameters request

Add this content in bug description, using file upload or code block.

API requests catch notes

The wanted requests are:

  • The one done on https://api.monpetitgazon.com/ (some requests can have the same suffix if you are using the search filter) ; details can be found in Headers tab of network monitor
  • The GET or POST http verbs. The OPTIONS http verbs are used for other needs in API usage and useless for bugs analysis

Clone this wiki locally