https://bz.apache.org/bugzilla/show_bug.cgi?id=58789
--- Comment #6 from William A. Rowe Jr. <[email protected]> --- I don't immediately see the cause. The config merge logic is correct, the broader (global/vhost/<Directory />) scopes are added before sub-scopes (nested directories, Files etc). It almost sounds like you used setifempty; "The request header is set, but only if there is no previous header with this name. Available in 2.4.7 and later." because the first Header set in the list will cause later setifempty assignments to fail even if they are in a more precise scope. We process the list sequentially. The problem would also occur if you used 'early', e.g. Header set AAA XXXXXXXX early "Because early directives are processed before the request path's configuration is traversed, early headers can only be set in a main server or virtual host context. Early directives cannot depend on a request path, so they will fail in contexts such as <Directory> or <Location>." You didn't do either of these things, but they may provide a clue about where the bug may be hiding. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
