核心内容摘要
编写搜索引擎_搜索引擎开发指南：从原理到实现的完整教程
seo营销模式_SEO策略新路径：驱动增长的营销实战
Going beyond the power of HTTP request parameters, HttpClient provides a host of other configuration options. In most cases, you won't need to customize these. But in case you do, Maven provides access to specify your own fine-grained configuration for HttpClient. Again, you can specify these parameter customizations per-method (HEAD, GET, or PUT), or for all methods of interacting with a given server. For a complete list of supported parameters, see the link[2] in Resources section below. Many of the configuration parameters for HttpClient have simple string values; however, there are important exceptions to this. In some cases, you may need to specify boolean, integer, or long values. In others, you may even need to specify a collection of string values. You can specify these using a simple formatting syntax, as follows: booleans: integer: long: (yes, that's an ‘L’, not a ‘1’) double: collection of strings: , which could also be specified as: As you may have noticed, this syntax is similar to the format-and-data strategy used by functions like in many languages. The syntax has been chosen with this similarity in mind, to make it a little more intuitive to use. Example: Using Preemptive Authentication Using the above syntax, you can configure preemptive authentication for PUT requests using the boolean HttpClient parameter , like this: Another option is to make write it like this: Maven Wagon by default limits supplied credentials to the host:port combination scope, ignoring any other target servers. When the target server delegates authentication to an external system, you need to deliberately lift that scope limitation. Configure your server element to pass authentication to all target servers which challenge the client. +—+ settings servers server id_my-server/id_ configuration basicAuthScope host_ANY/host_ port_ANY/port_ !– or even 443 to force the use of TLS – /basicAuthScope httpConfiguration all params property name_http.protocol.cookie-policy/name_ value_standard/value_ /property /params /all /httpConfiguration /configuration /server /servers /settings +—+ Like the example above, telling the HttpClient to ignore cookies for all methods of request is a simple matter of configuring the parameter (it uses a regular string value, so no special syntax is required): The configuration above can be useful in cases where the repository is using cookies - like the session cookies that are often mistakenly turned on or left on in appservers - alongside HTTP redirection. In these cases, it becomes far more likely that the cookie issued by the appserver uses a that is inconsistent with the one used by the client to access the server. If you have this problem, and know that you don't need to use this session cookie, you can ignore cookies from this server with the above configuration.
