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
-
Activity
| Resolution | Done [ 10000 ] | |
| Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
| Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Rank | Ranked higher |
| Sprint | Fall 5 : 14 Oct to 25 Oct [ 76 ] | Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov [ 76, 77 ] |
| Assignee | Ann Loraine [ aloraine ] |
| Status | In Progress [ 3 ] | To-Do [ 10305 ] |
| Workflow | Fall 2019 Workflow Update [ 20812 ] | Revised Fall 2019 Workflow Update [ 21131 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| 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? * How much control do we have over the header? |
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? |
| 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/##### * How much control do we have over the header? |
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? * How much control do we have over the header? |
| 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. Also, 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/##### * How much control do we have over the header? |
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/##### * How much control do we have over the header? |
| Summary | Investigate: correct and useful user agent string for IGB to use | Investigate: What is the correct and useful user agent string for IGB to use? |
| Assignee | Ann Loraine [ aloraine ] |
| 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. Also, 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/##### |
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. Also, 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/##### * How much control do we have over the header? |
| 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. |
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. Also, 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/##### |
| Assignee | Ann Loraine [ aloraine ] |
| Description |
When IGB contacts a resource, IGB should identify itself by version and commit hash.
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. |
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. |
| Rank | Ranked higher |
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-1531 [ 17617 ] |