bd173c28fc
Nested domain-config inherit unset parameters from the domain-config they are nested in. This helps avoid copy and pasted configs that are almost the same except a few minor differences for a domain with slightly different requirements. For example: Consider a domain-config for example.com that, among other settings, does not enforce hsts. Now if you want the rules for example.com to apply to secure.example.com except that hsts _is_ enforced you can make a nested domain-config for secure.example.com under example.com that sets hstsEnforced="true" and nothing else. Change-Id: I9e33f7e62127fd7f4f15c3560fff2f2626477bd4
19 lines
615 B
XML
19 lines
615 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<network-security-config>
|
|
<domain-config>
|
|
<domain includeSubdomains="true">android.com</domain>
|
|
<trust-anchors>
|
|
<certificates src="system" />
|
|
</trust-anchors>
|
|
<!-- nested config that adds pins -->
|
|
<domain-config>
|
|
<domain>developer.android.com</domain>
|
|
<pin-set>
|
|
<pin digest="SHA-256">7HIpactkIAq2Y49orFOOQKurWxmmSFZhBCoQYcRhJ3Y=</pin>
|
|
</pin-set>
|
|
</domain-config>
|
|
</domain-config>
|
|
<base-config cleartextTrafficPermitted="false">
|
|
</base-config>
|
|
</network-security-config>
|