Support editing HTTP headers

bmohdz21 / google-refine

Automatically exported from code.google.com/p/google-refine

0 stars 0 forks source link

Support editing HTTP headers #218

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Find a closed API that requires API key as HTTP header
2. Oh noes! Can't enter API key.

What is the expected output? What do you see instead?
Happy data. Zilch.

Original issue reported on code.google.com by mcnamara.tim@gmail.com on 15 Nov 2010 at 10:19

GoogleCodeExporter commented 9 years ago

Issue 219 has been merged into this issue.

Original comment by iainsproat on 15 Nov 2010 at 10:31

GoogleCodeExporter commented 9 years ago

Original comment by tfmorris on 16 Nov 2010 at 5:58

Changed state: New
Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 9 years ago

Original comment by tfmorris on 16 Nov 2010 at 6:48

Changed title: Support editing HTTP headers

GoogleCodeExporter commented 9 years ago

Tim - Can you provide an example (or more than one) of an API which requires 
the key in the header (and doesn't provide an alternative like YouTube does)?

Another use case for this (or very similar) functionality is the "Accept: " 
header field for specifying data formats.  This is used by, for example, end 
points which can return either RDF or HTML (like rdf.freebase.com) as well as 
other multiformat APIs such as CrossRefs 
http://www.crossref.org/CrossTech/2011/11/turning_dois_into_formatted_ci.html

Original comment by tfmorris on 19 Dec 2011 at 11:19