-
Notifications
You must be signed in to change notification settings - Fork 821
/
custominstance.go
266 lines (252 loc) · 18.6 KB
/
custominstance.go
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
package customsearch
// Copyright (c) Microsoft and contributors. All rights reserved.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
//
// See the License for the specific language governing permissions and
// limitations under the License.
//
// Code generated by Microsoft (R) AutoRest Code Generator.
// Changes may cause incorrect behavior and will be lost if the code is regenerated.
import (
"context"
"github.com/Azure/go-autorest/autorest"
"github.com/Azure/go-autorest/autorest/azure"
"github.com/Azure/go-autorest/autorest/validation"
"net/http"
)
// CustomInstanceClient is the the Bing Custom Search API lets you send a search query to Bing and get back search
// results customized to meet your custom search definition.
type CustomInstanceClient struct {
BaseClient
}
// NewCustomInstanceClient creates an instance of the CustomInstanceClient client.
func NewCustomInstanceClient() CustomInstanceClient {
return NewCustomInstanceClientWithBaseURI(DefaultBaseURI)
}
// NewCustomInstanceClientWithBaseURI creates an instance of the CustomInstanceClient client.
func NewCustomInstanceClientWithBaseURI(baseURI string) CustomInstanceClient {
return CustomInstanceClient{NewWithBaseURI(baseURI)}
}
// Search sends the search request.
//
// customConfig is the identifier for the custom search configuration query is the user's search query term. The
// term may not be empty. The term may contain Bing Advanced Operators. For example, to limit results to a specific
// domain, use the site: operator. acceptLanguage is a comma-delimited list of one or more languages to use for
// user interface strings. The list is in decreasing order of preference. For additional information, including
// expected format, see [RFC2616](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html). This header and the
// setLang query parameter are mutually exclusive; do not specify both. If you set this header, you must also
// specify the cc query parameter. Bing will use the first supported language it finds from the list, and combine
// that language with the cc parameter value to determine the market to return results for. If the list does not
// include a supported language, Bing will find the closest language and market that supports the request, and may
// use an aggregated or default market for the results instead of a specified one. You should use this header and
// the cc query parameter only if you specify multiple languages; otherwise, you should use the mkt and setLang
// query parameters. A user interface string is a string that's used as a label in a user interface. There are very
// few user interface strings in the JSON response objects. Any links in the response objects to Bing.com
// properties will apply the specified language. userAgent is the user agent originating the request. Bing uses the
// user agent to provide mobile users with an optimized experience. Although optional, you are strongly encouraged
// to always specify this header. The user-agent should be the same string that any commonly used browser would
// send. For information about user agents, see [RFC 2616](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html).
// clientID is bing uses this header to provide users with consistent behavior across Bing API calls. Bing often
// flights new features and improvements, and it uses the client ID as a key for assigning traffic on different
// flights. If you do not use the same client ID for a user across multiple requests, then Bing may assign the user
// to multiple conflicting flights. Being assigned to multiple conflicting flights can lead to an inconsistent user
// experience. For example, if the second request has a different flight assignment than the first, the experience
// may be unexpected. Also, Bing can use the client ID to tailor web results to that client ID’s search history,
// providing a richer experience for the user. Bing also uses this header to help improve result rankings by
// analyzing the activity generated by a client ID. The relevance improvements help with better quality of results
// delivered by Bing APIs and in turn enables higher click-through rates for the API consumer. IMPORTANT: Although
// optional, you should consider this header required. Persisting the client ID across multiple requests for the
// same end user and device combination enables 1) the API consumer to receive a consistent user experience, and 2)
// higher click-through rates via better quality of results from the Bing APIs. Each user that uses your
// application on the device must have a unique, Bing generated client ID. If you do not include this header in the
// request, Bing generates an ID and returns it in the X-MSEdge-ClientID response header. The only time that you
// should NOT include this header in a request is the first time the user uses your app on that device. Use the
// client ID for each Bing API request that your app makes for this user on the device. Persist the client ID. To
// persist the ID in a browser app, use a persistent HTTP cookie to ensure the ID is used across all sessions. Do
// not use a session cookie. For other apps such as mobile apps, use the device's persistent storage to persist the
// ID. The next time the user uses your app on that device, get the client ID that you persisted. Bing responses
// may or may not include this header. If the response includes this header, capture the client ID and use it for
// all subsequent Bing requests for the user on that device. If you include the X-MSEdge-ClientID, you must not
// include cookies in the request. clientIP is the IPv4 or IPv6 address of the client device. The IP address is
// used to discover the user's location. Bing uses the location information to determine safe search behavior.
// Although optional, you are encouraged to always specify this header and the X-Search-Location header. Do not
// obfuscate the address (for example, by changing the last octet to 0). Obfuscating the address results in the
// location not being anywhere near the device's actual location, which may result in Bing serving erroneous
// results. location is a semicolon-delimited list of key/value pairs that describe the client's geographical
// location. Bing uses the location information to determine safe search behavior and to return relevant local
// content. Specify the key/value pair as <key>:<value>. The following are the keys that you use to specify the
// user's location. lat (required): The latitude of the client's location, in degrees. The latitude must be greater
// than or equal to -90.0 and less than or equal to +90.0. Negative values indicate southern latitudes and positive
// values indicate northern latitudes. long (required): The longitude of the client's location, in degrees. The
// longitude must be greater than or equal to -180.0 and less than or equal to +180.0. Negative values indicate
// western longitudes and positive values indicate eastern longitudes. re (required): The radius, in meters, which
// specifies the horizontal accuracy of the coordinates. Pass the value returned by the device's location service.
// Typical values might be 22m for GPS/Wi-Fi, 380m for cell tower triangulation, and 18,000m for reverse IP lookup.
// ts (optional): The UTC UNIX timestamp of when the client was at the location. (The UNIX timestamp is the number
// of seconds since January 1, 1970.) head (optional): The client's relative heading or direction of travel.
// Specify the direction of travel as degrees from 0 through 360, counting clockwise relative to true north.
// Specify this key only if the sp key is nonzero. sp (optional): The horizontal velocity (speed), in meters per
// second, that the client device is traveling. alt (optional): The altitude of the client device, in meters. are
// (optional): The radius, in meters, that specifies the vertical accuracy of the coordinates. Specify this key
// only if you specify the alt key. Although many of the keys are optional, the more information that you provide,
// the more accurate the location results are. Although optional, you are encouraged to always specify the user's
// geographical location. Providing the location is especially important if the client's IP address does not
// accurately reflect the user's physical location (for example, if the client uses VPN). For optimal results, you
// should include this header and the X-MSEdge-ClientIP header, but at a minimum, you should include this header.
// countryCode is a 2-character country code of the country where the results come from. This API supports only the
// United States market. If you specify this query parameter, it must be set to us. If you set this parameter, you
// must also specify the Accept-Language header. Bing uses the first supported language it finds from the languages
// list, and combine that language with the country code that you specify to determine the market to return results
// for. If the languages list does not include a supported language, Bing finds the closest language and market
// that supports the request, or it may use an aggregated or default market for the results instead of a specified
// one. You should use this query parameter and the Accept-Language query parameter only if you specify multiple
// languages; otherwise, you should use the mkt and setLang query parameters. This parameter and the mkt query
// parameter are mutually exclusive—do not specify both. count is the number of search results to return in the
// response. The default is 10 and the maximum value is 50. The actual number delivered may be less than
// requested.Use this parameter along with the offset parameter to page results.For example, if your user interface
// displays 10 search results per page, set count to 10 and offset to 0 to get the first page of results. For each
// subsequent page, increment offset by 10 (for example, 0, 10, 20). It is possible for multiple pages to include
// some overlap in results. market is the market where the results come from. Typically, mkt is the country where
// the user is making the request from. However, it could be a different country if the user is not located in a
// country where Bing delivers results. The market must be in the form <language code>-<country code>. For example,
// en-US. The string is case insensitive. If known, you are encouraged to always specify the market. Specifying the
// market helps Bing route the request and return an appropriate and optimal response. If you specify a market that
// is not listed in Market Codes, Bing uses a best fit market code based on an internal mapping that is subject to
// change. This parameter and the cc query parameter are mutually exclusive—do not specify both. offset is the
// zero-based offset that indicates the number of search results to skip before returning results. The default is
// 0. The offset should be less than (totalEstimatedMatches - count). Use this parameter along with the count
// parameter to page results. For example, if your user interface displays 10 search results per page, set count to
// 10 and offset to 0 to get the first page of results. For each subsequent page, increment offset by 10 (for
// example, 0, 10, 20). it is possible for multiple pages to include some overlap in results. safeSearch is a
// filter used to filter adult content. Off: Return webpages with adult text, images, or videos. Moderate: Return
// webpages with adult text, but not adult images or videos. Strict: Do not return webpages with adult text,
// images, or videos. The default is Moderate. If the request comes from a market that Bing's adult policy requires
// that safeSearch is set to Strict, Bing ignores the safeSearch value and uses Strict. If you use the site: query
// operator, there is the chance that the response may contain adult content regardless of what the safeSearch
// query parameter is set to. Use site: only if you are aware of the content on the site and your scenario supports
// the possibility of adult content. setLang is the language to use for user interface strings. Specify the
// language using the ISO 639-1 2-letter language code. For example, the language code for English is EN. The
// default is EN (English). Although optional, you should always specify the language. Typically, you set setLang
// to the same language specified by mkt unless the user wants the user interface strings displayed in a different
// language. This parameter and the Accept-Language header are mutually exclusive; do not specify both. A user
// interface string is a string that's used as a label in a user interface. There are few user interface strings in
// the JSON response objects. Also, any links to Bing.com properties in the response objects apply the specified
// language. textDecorations is a Boolean value that determines whether display strings should contain decoration
// markers such as hit highlighting characters. If true, the strings may include markers. The default is false. To
// specify whether to use Unicode characters or HTML tags as the markers, see the textFormat query parameter.
// textFormat is the type of markers to use for text decorations (see the textDecorations query parameter).
// Possible values are Raw—Use Unicode characters to mark content that needs special formatting. The Unicode
// characters are in the range E000 through E019. For example, Bing uses E000 and E001 to mark the beginning and
// end of query terms for hit highlighting. HTML—Use HTML tags to mark content that needs special formatting. For
// example, use <b> tags to highlight query terms in display strings. The default is Raw. For display strings that
// contain escapable HTML characters such as <, >, and &, if textFormat is set to HTML, Bing escapes the characters
// as appropriate (for example, < is escaped to <).
func (client CustomInstanceClient) Search(ctx context.Context, customConfig int64, query string, acceptLanguage string, userAgent string, clientID string, clientIP string, location string, countryCode string, count *int32, market string, offset *int32, safeSearch SafeSearch, setLang string, textDecorations *bool, textFormat TextFormat) (result SearchResponse, err error) {
if err := validation.Validate([]validation.Validation{
{TargetValue: customConfig,
Constraints: []validation.Constraint{{Target: "customConfig", Name: validation.InclusiveMinimum, Rule: 0, Chain: nil}}}}); err != nil {
return result, validation.NewError("customsearch.CustomInstanceClient", "Search", err.Error())
}
req, err := client.SearchPreparer(ctx, customConfig, query, acceptLanguage, userAgent, clientID, clientIP, location, countryCode, count, market, offset, safeSearch, setLang, textDecorations, textFormat)
if err != nil {
err = autorest.NewErrorWithError(err, "customsearch.CustomInstanceClient", "Search", nil, "Failure preparing request")
return
}
resp, err := client.SearchSender(req)
if err != nil {
result.Response = autorest.Response{Response: resp}
err = autorest.NewErrorWithError(err, "customsearch.CustomInstanceClient", "Search", resp, "Failure sending request")
return
}
result, err = client.SearchResponder(resp)
if err != nil {
err = autorest.NewErrorWithError(err, "customsearch.CustomInstanceClient", "Search", resp, "Failure responding to request")
}
return
}
// SearchPreparer prepares the Search request.
func (client CustomInstanceClient) SearchPreparer(ctx context.Context, customConfig int64, query string, acceptLanguage string, userAgent string, clientID string, clientIP string, location string, countryCode string, count *int32, market string, offset *int32, safeSearch SafeSearch, setLang string, textDecorations *bool, textFormat TextFormat) (*http.Request, error) {
queryParameters := map[string]interface{}{
"customConfig": autorest.Encode("query", customConfig),
"q": autorest.Encode("query", query),
}
if len(countryCode) > 0 {
queryParameters["cc"] = autorest.Encode("query", countryCode)
}
if count != nil {
queryParameters["count"] = autorest.Encode("query", *count)
}
if len(market) > 0 {
queryParameters["mkt"] = autorest.Encode("query", market)
} else {
queryParameters["mkt"] = autorest.Encode("query", "en-us")
}
if offset != nil {
queryParameters["offset"] = autorest.Encode("query", *offset)
}
if len(string(safeSearch)) > 0 {
queryParameters["safeSearch"] = autorest.Encode("query", safeSearch)
}
if len(setLang) > 0 {
queryParameters["setLang"] = autorest.Encode("query", setLang)
}
if textDecorations != nil {
queryParameters["textDecorations"] = autorest.Encode("query", *textDecorations)
}
if len(string(textFormat)) > 0 {
queryParameters["textFormat"] = autorest.Encode("query", textFormat)
}
preparer := autorest.CreatePreparer(
autorest.AsGet(),
autorest.WithBaseURL(client.BaseURI),
autorest.WithPath("/search"),
autorest.WithQueryParameters(queryParameters),
autorest.WithHeader("X-BingApis-SDK", "true"))
if len(acceptLanguage) > 0 {
preparer = autorest.DecoratePreparer(preparer,
autorest.WithHeader("Accept-Language", autorest.String(acceptLanguage)))
}
if len(userAgent) > 0 {
preparer = autorest.DecoratePreparer(preparer,
autorest.WithHeader("User-Agent", autorest.String(userAgent)))
}
if len(clientID) > 0 {
preparer = autorest.DecoratePreparer(preparer,
autorest.WithHeader("X-MSEdge-ClientID", autorest.String(clientID)))
}
if len(clientIP) > 0 {
preparer = autorest.DecoratePreparer(preparer,
autorest.WithHeader("X-MSEdge-ClientIP", autorest.String(clientIP)))
}
if len(location) > 0 {
preparer = autorest.DecoratePreparer(preparer,
autorest.WithHeader("X-Search-Location", autorest.String(location)))
}
return preparer.Prepare((&http.Request{}).WithContext(ctx))
}
// SearchSender sends the Search request. The method will close the
// http.Response Body if it receives an error.
func (client CustomInstanceClient) SearchSender(req *http.Request) (*http.Response, error) {
return autorest.SendWithSender(client, req,
autorest.DoRetryForStatusCodes(client.RetryAttempts, client.RetryDuration, autorest.StatusCodesForRetry...))
}
// SearchResponder handles the response to the Search request. The method always
// closes the http.Response Body.
func (client CustomInstanceClient) SearchResponder(resp *http.Response) (result SearchResponse, err error) {
err = autorest.Respond(
resp,
client.ByInspecting(),
azure.WithErrorUnlessStatusCode(http.StatusOK),
autorest.ByUnmarshallingJSON(&result),
autorest.ByClosing())
result.Response = autorest.Response{Response: resp}
return
}