The core feature of hiproxy is forwarding request. Hiproxy purposes to solve some problems which front-end developer can meet while working:
hostscannot work immediately since there are caches after it’s updated.
- Nginx is used for reverse proxy.
- Self signed HTTPS certificate are not trusted.
- Everyone maintans the environment profile (hosts/nginx configuration).
They all have the ability to capture packages, proxy request and many core function. But hiproxy is a CLI tool which works with configuration files.
However, hiproxy has no interface to see the specific content of request. That will be introduced as a plugin in the future.
They are no relationship actually.
the hosts file for hiproxy is normally placed in project directory, or other (user specified) directory. Hiproxy would looking for, load and parse the hosts file in project directories, but not do with OS one.
No. They are no relationship actually.
The rewrite configuration for rewrite has similar syntax of Nginx configuration. The core syntax is consistent with the syntax of Nginx, but there are also some syntax are specific to hiproxy. They are not exactly consistent with Nginx syntax. For example:
# base rule
In addition, some directives come from Nginx which do simular things, such as
ssl_certificate_key, etc. In any case they cannot promise that all details are same as Nginx directives.Please see Directive for more information.
Does hiproxy support that the same domain name is used in the configuration files of multi-projects?
You can set rules for the same domain name in configuration files of different projects. Hiproxy can merge all rules about the same domains. If there is conflict, later loaded rules would rewrite earlier rules.
By default, when the https request is forwading, hiproxy will generate the certifiate automatically and use customized CA certificate signature. The users should import root certificate of hiproxy.
If you use customized certificate, ou can use some hiproxy directive for configurating: