Skip to main content
Geographic Information Systems

Return to Answer

added 4 characters in body
Source Link
Shimon Cohen
Shimon Cohen
  • 138
  • 5

Looks like this is currently not possible in Mapproxy - https://github.com/mapproxy/mapproxy/issues/206. The

The referenced issue's thread mentions that the need for subdomains is typically used as a workaround for browser limitations (Max parallel HTTP connections in a browser?), but i am not sure why this is a good reason for not supporting the feature when you want to be able to server common browsers as fast as possible... A

A possible solution will be to implement the same behavior by using HTTP2 (HTTP2 VS HTTP1), which has this as a default (HTTP2 multiplexing).

Looks like this is currently not possible in Mapproxy - https://github.com/mapproxy/mapproxy/issues/206. The referenced issue's thread mentions that the need for subdomains is typically used as a workaround for browser limitations (Max parallel HTTP connections in a browser?), but i am not sure why this is a good reason for not supporting the feature when you want to be able to server common browsers as fast as possible... A possible solution will be to implement the same behavior by using HTTP2 (HTTP2 VS HTTP1), which has this as a default (HTTP2 multiplexing).

Looks like this is currently not possible in Mapproxy - https://github.com/mapproxy/mapproxy/issues/206.

The referenced issue's thread mentions that the need for subdomains is typically used as a workaround for browser limitations (Max parallel HTTP connections in a browser?), but i am not sure why this is a good reason for not supporting the feature when you want to be able to server common browsers as fast as possible...

A possible solution will be to implement the same behavior by using HTTP2 (HTTP2 VS HTTP1), which has this as a default (HTTP2 multiplexing).

Source Link
Shimon Cohen
Shimon Cohen
  • 138
  • 5

Looks like this is currently not possible in Mapproxy - https://github.com/mapproxy/mapproxy/issues/206. The referenced issue's thread mentions that the need for subdomains is typically used as a workaround for browser limitations (Max parallel HTTP connections in a browser?), but i am not sure why this is a good reason for not supporting the feature when you want to be able to server common browsers as fast as possible... A possible solution will be to implement the same behavior by using HTTP2 (HTTP2 VS HTTP1), which has this as a default (HTTP2 multiplexing).