DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33944>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33944 ------- Additional Comments From [EMAIL PROTECTED] 2005-04-08 19:20 ------- (In reply to comment #4) > It appears that you are right - that the ASP.NET module with .NET 1.1 does > set 'X-AspNet-Version'. I suspect from my early tests that .NET 1.0 did not. > > We can still handle this, but should ensure that X-AspNet-Version specifically > does not merge headers, but instead overwrites the value. Some, like Cookie, > must merge. Many other headers should not. > What I can't understand is what is responsible for sending the header. With NO modifications to the httpd.conf or to the asp.net module itself the 'X-AspNet-Version' header is being sent under Apache on my machine when handling Asp.Net pages. As I stated initially this was not the case before. So what I'm trying to get across is this may not be a bug or feature limitation at all or if it is it is only present under certain circumstances which I can't figure out a cause of. So to lay out my experience up to this point: 1. ASP.Net on Apache works just like Asp.Net on IIS except VS.Net thinks that projects opened on Apache server are ASP 1.0. 2. Realize the only difference in responses is 'X-AspNet-Version' header is missing from Apache response. 3. Modify httpd.conf to send 'X-AspNet-Version: 1.1.4322' 4. VS works as it should. 5. File this bug 6. Check headers later and notice 'X-AspNet-Version: 1.1.4322,1.1.4322' 7. Remove statement in httpd.conf. 8. Header is sent but WITHOUT duplicate version numbers 9. Everything still works fine with no modifications -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
