global service HTTP request identification

[tomkralidis]

Currently, the GB RI is sending requests to the GDC to assemble record lookups by centre-ids.

For access log filtering, it would be valuable for Global Services who are interacting with one another, where applicable, to identify as a global service when invoking HTTP requests.

Options:

1. set HTTP User-Agent header (centre-name/centre-id). Example: Météo-France, Global Broker Service, (fr-meteo-france-global-broker)
2. set a well-defined HTTP query parameter. Example: &wis2-centre-id=fr-meteo-france-global-broker
3. other options?

Option 1 is ideal.

We can clarify in the Guide for "internal global service traffic".

[golfvert]

Not sure I understand why it is useful / important.
It is already possible anyway. The GB and others are sharing the IP addresses they are using. Isn't it sufficient to use the source IP in the logs ?

[tomkralidis]

Not sure I understand why it is useful / important.

For example, the GDC needs to assess "real" user traffic (vs. other global services)

It is already possible anyway. The GB and others are sharing the IP addresses they are using. Isn't it sufficient to use the source IP in the logs ?

Then the GDC would need to be configured/setup/updated to deal with IP addresses. Having clients properly identify themselves via HTTP headers adds values and reduces maintenance.