How a feed client pushes a feed – Google Search Appliance Feeds Protocol Developers Guide User Manual
Page 29
Google Search Appliance: Feeds Protocol Developer’s Guide
29
To adapt this form for your search appliance, replace APPLIANCE-HOSTNAME with the fully qualified
domain name of your search appliance.
<html>
<head>
<title>Simple form for pushing a feed</title>
</head>
<body>
<h1>Simple form for pushing a feed</h1>
<form enctype="multipart/form-data" method=POST
action="http://<APPLIANCE-HOSTNAME>:19900/xmlfeed">
<p>Name of datasource:
<input type="text" name="datasource">
<br>
(No spaces or non alphanumeric characters)
</p>
<p>Type of feed:
<input type="radio" name="feedtype" value="full" checked>
Full
<input type="radio" name="feedtype" value="incremental">
Incremental
<input type="radio" name="feedtype" value="metadata-and-url">
Metadata and URL
</p>
<p>
XML file to push:
<input type="file" name="data">
</p>
<p>
<input type="submit" value=">Submit<">
</p>
</form>
</body>
</html>
How a Feed Client Pushes a Feed
When pushing a feed, the feed client sends the POST data to a search appliance. A typical POST from a
scripted feed client appears as follows:
POST /xmlfeed HTTP/1.0
Content-type: multipart/form-data
Content-length: 855
Host: myserver.domain.com:19900
User-agent: Python-urllib/1.15
feedtype=full&datasource=sample&data=%3C%3Fxml+version%3D%221.0%22+encoding%3D%2
2UTF-8%22%3F%3E%0A%3C%21DOCTYPE+gsafeed+SYSTEM+..
The response from the search appliance is as follows:
HTTP/1.0 200 OK
Content-Type: text/plain
Date: Thu, 30 Apr 2009 23:16:10 GMT
Server: feedergate_1.0
Connection: Close
Content-Length: 7
Success