Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Sprint:Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov
Description
When IGB contacts a resource, IGB should identify itself in useful ways.
For example, if an IGB instance hits an App Store and tries to download a jar or other resource, we could configure our S3 to reply to IGB only, using the user-agent to determine if the client is IGB or not.
Investigate:
Can we include this information in the HTTP header somehow?
Is IGB currently using a user agent string?
Investigate:
What headers is IGB using currently?
Use Postman to "spy on" network traffic coming to and from IGB. Report back here.
Investigate:
- What is the convention for an application?
For example, would it be considered weird or uncool to add a commit hash, e.g,
IGB/9.0.1/#####? What about an API key or something that gets decided programmatically when a user downloads and installs IGB? - How much control do we have over the header?
Attachments
Issue Links
- relates to
-
-
- Closed
-