The hosted FaxService operation constructs a hand-written wrapper, FaxServiceProxy, which builds its own binding and endpoint address in code and constructs the generated FaxServiceSoapClient directly, bypassing the configured <client><endpoint> entirely.
MaxReceivedMessageSize, MaxBufferSize, and ReaderQuotas.MaxArrayLength are all set to int.MaxValue, removing the guard that protects the process from an oversized response; see Tech debt.
The string returned by env.GetConfigSetting(EnvironmentConfigKeys.FaxSoapServiceUrl)
src\WCF\SAIF.Services.WCF.Host\Services\FaxService.cs:21-25, passed through src\WCF\SAIF.Services.WCF.Host\Services\LegacyProxies\FaxServiceProxy.cs:12,29; the literal key name and its per-environment values are supplied by the referenced SAIF.Services.Common package assembly and are unresolvable in this repository**
Yes — resolved per request from the environment service*
Two findings on this table, recorded once and cross-referenced from Tech debt: the configured <client><endpoint> is never consulted at run time because the wrapper supplies its own binding and address, and two stale endpoint declarations (api.saif.com and websvcprod) coexist with the third, authoritative, code-resolved address whose literal key name cannot be read from this repository**.
Per FaxServiceProxy instance, which is itself constructed once per FaxService instance and held in a readonly field
Disposal
Close() only, with no Abort() fallback
Faulted-channel handling
Not handled — ClientBase<T>.Close() on a faulted channel throws, so a failed Send can produce a second exception during disposal and mask the original failure*
Note: Statements marked with † are derived from dependency library documentation via the Legends CLI. Statements marked with * were inferred from code structure or contextual evidence. Statements marked with ** could not be confirmed; treat as unknown until verified.