Difference: SoftID (1 vs. 7)

Revision 72021-06-29 - MarkTaylor

 
META TOPICPARENT name="UserAgentUsage"

Software Identification

This page collects resources related to activities of the Operations Iterest Group concerning identification in client/server interactions.

History

This topic was kicked off by discussions at Interops (Mark in College Park, Markus in Groningen). It concerns recommendations for best practice in use of the HTTP User-Agent and Server headers so that clients (especially "operational-mode" clients such as validators) and servers can be identified by other software they are interacting with. Recommendations for client identification were initially codified on the UserAgentUsage page.

Status:

This is now a published IVOA Note: NOTE-softid-1.0.

Takeup

This section lists examples of client and server headers written by some known VO components, that may or may not follow the SoftID recommendations. Please note the examples are representative, not necessarily verbatim copies of what these components will report.

If you can add entries to this list, please do. You can add as much information as seems relevant, e.g. dates or versions for which certain header values apply (where it's not obvious from the context).

Client software (User-Agent header)

  • STILTS validation tools (taplint, datalinklint)
Changed:
<
<
    • User-Agent: STILTS/3.4 (IVOA-validate) Java/1.8.0_181
>
>
    • User-Agent: STILTS/3.4 (IVOA-validate) Java/1.8.0_181 (earlier versions, following earlier softid draft)
Added:
>
>
    • User-Agent: STILTS/3.4-1+ (IVOA-test) Java/1.8.0_181 (later versions, following published Note-softid-1.0)
 
  • STILTS general query tools (tapquery, cone)
    • User-Agent: STILTS/3.4 Java/1.8.0_181
  • TOPCAT
    • User-Agent: TOPCAT/4.8 Java/1.8.0_181
  • GloTS
    • User-Agent: GloTS-harvester (IVOA-copy) DaCHS/{version}
  • GAVO RegTAP
    • User-Agent: GAVO-RegTAP-harvester (IVOA-copy) DaCHS/{version}

Server software (Server header)

  • DaCHS over twisted:
    • Server: DaCHS/{version} twistedWeb/{version}


<--  
-->

Revision 62021-06-16 - MarkTaylor

 
META TOPICPARENT name="UserAgentUsage"

Software Identification

This page collects resources related to activities of the Operations Iterest Group concerning identification in client/server interactions.

History

This topic was kicked off by discussions at Interops (Mark in College Park, Markus in Groningen). It concerns recommendations for best practice in use of the HTTP User-Agent and Server headers so that clients (especially "operational-mode" clients such as validators) and servers can be identified by other software they are interacting with. Recommendations for client identification were initially codified on the UserAgentUsage page.

Changed:
<
<

Status

>
>

Status:

 
Changed:
<
<
Thinking on this topic has been written up into a draft IVOA Note edited by Markus Demleitner. This document currently lives at https://github.com/msdemlei/softid, with a formatted version that may be available at http://docs.g-vo.org/softid.pdf.
>
>
This is now a published IVOA Note: NOTE-softid-1.0.
 

Takeup

This section lists examples of client and server headers written by some known VO components, that may or may not follow the SoftID recommendations. Please note the examples are representative, not necessarily verbatim copies of what these components will report.

If you can add entries to this list, please do. You can add as much information as seems relevant, e.g. dates or versions for which certain header values apply (where it's not obvious from the context).

Client software (User-Agent header)

  • STILTS validation tools (taplint, datalinklint)
    • User-Agent: STILTS/3.4 (IVOA-validate) Java/1.8.0_181
  • STILTS general query tools (tapquery, cone)
    • User-Agent: STILTS/3.4 Java/1.8.0_181
  • TOPCAT
    • User-Agent: TOPCAT/4.8 Java/1.8.0_181
  • GloTS
    • User-Agent: GloTS-harvester (IVOA-copy) DaCHS/{version}
  • GAVO RegTAP
    • User-Agent: GAVO-RegTAP-harvester (IVOA-copy) DaCHS/{version}

Server software (Server header)

  • DaCHS over twisted:
    • Server: DaCHS/{version} twistedWeb/{version}


<--  
-->

Revision 52021-05-27 - MarkusDemleitner

 
META TOPICPARENT name="UserAgentUsage"

Software Identification

This page collects resources related to activities of the Operations Iterest Group concerning identification in client/server interactions.

History

This topic was kicked off by discussions at Interops (Mark in College Park, Markus in Groningen). It concerns recommendations for best practice in use of the HTTP User-Agent and Server headers so that clients (especially "operational-mode" clients such as validators) and servers can be identified by other software they are interacting with. Recommendations for client identification were initially codified on the UserAgentUsage page.

Status

Thinking on this topic has been written up into a draft IVOA Note edited by Markus Demleitner. This document currently lives at https://github.com/msdemlei/softid, with a formatted version that may be available at http://docs.g-vo.org/softid.pdf.

Takeup

This section lists examples of client and server headers written by some known VO components, that may or may not follow the SoftID recommendations. Please note the examples are representative, not necessarily verbatim copies of what these components will report.

If you can add entries to this list, please do. You can add as much information as seems relevant, e.g. dates or versions for which certain header values apply (where it's not obvious from the context).

Client software (User-Agent header)

  • STILTS validation tools (taplint, datalinklint)
    • User-Agent: STILTS/3.4 (IVOA-validate) Java/1.8.0_181
  • STILTS general query tools (tapquery, cone)
    • User-Agent: STILTS/3.4 Java/1.8.0_181
  • TOPCAT
    • User-Agent: TOPCAT/4.8 Java/1.8.0_181
  • GloTS
Changed:
<
<
    • User-Agent: GloTS harvester (IVOA-copy) DaCHS {version}
>
>
    • User-Agent: GloTS-harvester (IVOA-copy) DaCHS/{version}
 
  • GAVO RegTAP
Changed:
<
<
    • User-Agent: GAVO RegTAP harvester (IVOA-copy) DaCHS {version}
>
>
    • User-Agent: GAVO-RegTAP-harvester (IVOA-copy) DaCHS/{version}
 

Server software (Server header)

  • DaCHS over twisted:
    • Server: DaCHS/{version} twistedWeb/{version}


<--  
-->

Revision 42021-03-10 - MarkusDemleitner

 
META TOPICPARENT name="UserAgentUsage"

Software Identification

This page collects resources related to activities of the Operations Iterest Group concerning identification in client/server interactions.

History

This topic was kicked off by discussions at Interops (Mark in College Park, Markus in Groningen). It concerns recommendations for best practice in use of the HTTP User-Agent and Server headers so that clients (especially "operational-mode" clients such as validators) and servers can be identified by other software they are interacting with. Recommendations for client identification were initially codified on the UserAgentUsage page.

Status

Thinking on this topic has been written up into a draft IVOA Note edited by Markus Demleitner. This document currently lives at https://github.com/msdemlei/softid, with a formatted version that may be available at http://docs.g-vo.org/softid.pdf.

Takeup

This section lists examples of client and server headers written by some known VO components, that may or may not follow the SoftID recommendations. Please note the examples are representative, not necessarily verbatim copies of what these components will report.

If you can add entries to this list, please do. You can add as much information as seems relevant, e.g. dates or versions for which certain header values apply (where it's not obvious from the context).

Client software (User-Agent header)

  • STILTS validation tools (taplint, datalinklint)
    • User-Agent: STILTS/3.4 (IVOA-validate) Java/1.8.0_181
  • STILTS general query tools (tapquery, cone)
    • User-Agent: STILTS/3.4 Java/1.8.0_181
  • TOPCAT
    • User-Agent: TOPCAT/4.8 Java/1.8.0_181
  • GloTS
Changed:
<
<
    • User-Agent: GloTS harvester (IVOA-copy) DaCHS {version}
>
>
    • User-Agent: GloTS harvester (IVOA-copy) DaCHS {version}
 
  • GAVO RegTAP
Changed:
<
<
    • User-Agent: GAVO RegTAP harvester (IVOA-copy) DaCHS {version}
>
>
    • User-Agent: GAVO RegTAP harvester (IVOA-copy) DaCHS {version}
 

Server software (Server header)

Changed:
<
<
  • DaCHS over twisted:
    • Server: DaCHS/{version} twistedWeb/{version}
>
>
  • DaCHS over twisted:
    • Server: DaCHS/{version} twistedWeb/{version}
 


<--  
-->

Revision 32021-03-09 - MarkusDemleitner

 
META TOPICPARENT name="UserAgentUsage"

Software Identification

This page collects resources related to activities of the Operations Iterest Group concerning identification in client/server interactions.

History

This topic was kicked off by discussions at Interops (Mark in College Park, Markus in Groningen). It concerns recommendations for best practice in use of the HTTP User-Agent and Server headers so that clients (especially "operational-mode" clients such as validators) and servers can be identified by other software they are interacting with. Recommendations for client identification were initially codified on the UserAgentUsage page.

Status

Thinking on this topic has been written up into a draft IVOA Note edited by Markus Demleitner. This document currently lives at https://github.com/msdemlei/softid, with a formatted version that may be available at http://docs.g-vo.org/softid.pdf.

Takeup

This section lists examples of client and server headers written by some known VO components, that may or may not follow the SoftID recommendations. Please note the examples are representative, not necessarily verbatim copies of what these components will report.

If you can add entries to this list, please do. You can add as much information as seems relevant, e.g. dates or versions for which certain header values apply (where it's not obvious from the context).

Client software (User-Agent header)

  • STILTS validation tools (taplint, datalinklint)
    • User-Agent: STILTS/3.4 (IVOA-validate) Java/1.8.0_181
  • STILTS general query tools (tapquery, cone)
    • User-Agent: STILTS/3.4 Java/1.8.0_181
  • TOPCAT
    • User-Agent: TOPCAT/4.8 Java/1.8.0_181
Added:
>
>
  • GloTS
    • User-Agent: GloTS harvester (IVOA-copy) DaCHS {version}
  • GAVO RegTAP
    • User-Agent: GAVO RegTAP harvester (IVOA-copy) DaCHS {version}
 

Server software (Server header)

Changed:
<
<
>
>
Added:
>
>
    • Server: DaCHS/{version} twistedWeb/{version}
 


<--  
-->

Revision 22021-03-09 - MarkTaylor

 
META TOPICPARENT name="UserAgentUsage"

Software Identification

This page collects resources related to activities of the Operations Iterest Group concerning identification in client/server interactions.

History

This topic was kicked off by discussions at Interops (Mark in College Park, Markus in Groningen). It concerns recommendations for best practice in use of the HTTP User-Agent and Server headers so that clients (especially "operational-mode" clients such as validators) and servers can be identified by other software they are interacting with. Recommendations for client identification were initially codified on the UserAgentUsage page.

Status

Thinking on this topic has been written up into a draft IVOA Note edited by Markus Demleitner. This document currently lives at https://github.com/msdemlei/softid, with a formatted version that may be available at http://docs.g-vo.org/softid.pdf.

Takeup

This section lists examples of client and server headers written by some known VO components, that may or may not follow the SoftID recommendations. Please note the examples are representative, not necessarily verbatim copies of what these components will report.

Changed:
<
<
If you can add entries to this list, please do.
>
>
If you can add entries to this list, please do. You can add as much information as seems relevant, e.g. dates or versions for which certain header values apply (where it's not obvious from the context).
 

Client software (User-Agent header)

  • STILTS validation tools (taplint, datalinklint)
    • User-Agent: STILTS/3.4 (IVOA-validate) Java/1.8.0_181
  • STILTS general query tools (tapquery, cone)
    • User-Agent: STILTS/3.4 Java/1.8.0_181
  • TOPCAT
    • User-Agent: TOPCAT/4.8 Java/1.8.0_181

Server software (Server header)


<--  
-->

Revision 12021-03-08 - MarkTaylor

 
META TOPICPARENT name="UserAgentUsage"

Software Identification

This page collects resources related to activities of the Operations Iterest Group concerning identification in client/server interactions.

History

This topic was kicked off by discussions at Interops (Mark in College Park, Markus in Groningen). It concerns recommendations for best practice in use of the HTTP User-Agent and Server headers so that clients (especially "operational-mode" clients such as validators) and servers can be identified by other software they are interacting with. Recommendations for client identification were initially codified on the UserAgentUsage page.

Status

Thinking on this topic has been written up into a draft IVOA Note edited by Markus Demleitner. This document currently lives at https://github.com/msdemlei/softid, with a formatted version that may be available at http://docs.g-vo.org/softid.pdf.

Takeup

This section lists examples of client and server headers written by some known VO components, that may or may not follow the SoftID recommendations. Please note the examples are representative, not necessarily verbatim copies of what these components will report.

If you can add entries to this list, please do.

Client software (User-Agent header)

  • STILTS validation tools (taplint, datalinklint)
    • User-Agent: STILTS/3.4 (IVOA-validate) Java/1.8.0_181
  • STILTS general query tools (tapquery, cone)
    • User-Agent: STILTS/3.4 Java/1.8.0_181
  • TOPCAT
    • User-Agent: TOPCAT/4.8 Java/1.8.0_181

Server software (Server header)


<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback