jetnet

+1 for `_msearch` support :) The request body looks like this: ``` {"preference":"search"} {"query":{"bool":{"must":[{"bool":{"must":{"bool":{"should":[{"multi_match":{"query":"ai","fields":["content^1","author^5","description^1","title^10"],"type":"cross_fields","operator":"and"}},{"multi_match":{"query":"ai","fields":["content^1","author^5","description^1","title^10"],"type":"phrase_prefix","operator":"and"}}],"minimum_should_match":"1"}}}}]}},"highlight":{"pre_tags":[""],"post_tags":[""],"fields":{"content":{},"author":{},"description":{},"title":{}},"require_field_match":false},"size":20} ``` as it isn't a valid JSON request, I guess it cannot be parsed by `nboost`....

I'm not alone :) #596

maybe we could simplify the logic like following: I'd add two new options: * `

try this: ``` xml 200,301,302 ```

Thanks Pascal! I had no luck with Routing and ended up with a workaround using an environment variable, which is set to the site name in the `collector-http.sh`. I'll try...

same issue here. `secureScheme` helps with such sites, but unfortunately it cannot be used globally, as we have to crawl many unsecured sites too. Any suggestions? Thanks!

@PramodValavala-MSFT, really appreciate your clarification. Should I create a feature request or are you going to do that? Thanks!

/unresolve I think, it's an issue with the current implementation and NOT a feature request. Look, you cannot run `az command invoke` if your AKS user nodes have a taint....

one great example would be integrating [DeepDetect](https://www.deepdetect.com/models/) into content processing. an ExternalAPITagger would be: ``` ``` `INPUT_BASE64` - is the base64 encoded content. And the field `category` would contain all...

Thank you!