ability to rewrite location and cookies on v1-toolkit proxies

Bắt đầu với cấu hình proxy trong ionic.config.json và xem xét fork v1-toolkit-proxy-rewrite-location-and-cookie được liên kết. Kiểm tra cách CLI sử dụng http-proxy-middleware và xác định xem việc viết lại cookie-domain, viết lại Location, gỡ lỗi và các đích proxy động dựa trên đường dẫn có thể được xác định phạm vi cùng nhau hay không. Công việc được xem là hoàn tất khi có phạm vi tính năng đã thống nhất và một triển khai được chấp nhận cho các hành vi proxy đã chọn.

Our app runs ionic v1 and until now we used Chrome with some security settings turned off when testing our app in order to avoid most cross-origin issues like CORS and cookie samesite over HTTP when we call our REST API.

Recently Chrome 94 dropped support of some flags we really need like SameSiteByDefaultCookies or CookiesWithoutSameSiteMustBeSecure.

So we decided to use ionic's proxies feature which is configurable in ionic.config.json.

Unfortunately we went through some impediments:

1. one of our api does some redirection (like http://testserver 302-redirects to http://testserver/otherapi)
2. on production servers, some cookies have a domain set, which of course won't match the local test server entry point (usually http://localhost:8100)
3. we have a lot of different test servers, this would require a lot of entries in the proxies array.

To cover cases 1) and 2), we implemented new settings for the proxy (development has started on a fork):

• cookieDomainRewrite: { [domain: string]: string }; turns on rewriting cookie domain on set-cookie headers
• locationRewrite: boolean turns on rewriting location host+port AND path on redirection. For example if you proxy /api to http://testserver then a header Location: http://testserver/otherapi would be rewritten to Location: http://localhost:8100/api/otherapi.
• debug: boolean turns on verbose debugging of http-proxy-middleware

I know v1 is quite old, but could these features be of interest for other users and so we might open a pull request ? Or maybe you have some suggestions ?

For case 3) we are willing to implement dynamic proxy based on path. The idea is to redirect on a different server based on a part of the path. Something that would be configurable this way:

{
      "path": "/api/*",
      "proxyUrl": "http://$1/"
}