Call for Presentations now open, ApacheCon North America 2022
[You are receiving this because you are subscribed to one or more user or dev mailing list of an Apache Software Foundation project.] ApacheCon draws participants at all levels to explore “Tomorrow’s Technology Today” across 300+ Apache projects and their diverse communities. ApacheCon showcases the latest developments in ubiquitous Apache projects and emerging innovations through hands-on sessions, keynotes, real-world case studies, trainings, hackathons, community events, and more. The Apache Software Foundation will be holding ApacheCon North America 2022 at the New Orleans Sheration, October 3rd through 6th, 2022. The Call for Presentations is now open, and will close at 00:01 UTC on May 23rd, 2022. We are accepting presentation proposals for any topic that is related to the Apache mission of producing free software for the public good. This includes, but is not limited to: Community Big Data Search IoT Cloud Fintech Pulsar Tomcat You can submit your session proposals starting today at https://cfp.apachecon.com/ Rich Bowen, on behalf of the ApacheCon Planners apachecon.com @apachecon
Re: HTTP and HTTP/1.x separation
> Am 28.03.2022 um 15:52 schrieb jean-frederic clere : > > On 24/03/2022 13:21, Stefan Eissing wrote: >> You are invited to have a look at my PR for separating HTTP/1.x processing >> from >> generic HTTP protocol handling and verification: >> https://github.com/apache/httpd/pull/291 >> I made a description of the changes in the PR that helps reviewing it (I >> hope). >> "Changes appear larger than they really are" >> A lot is code split+move from mod_http to mod_http1. In mod_http2, changes >> are >> mainly removals of quirks necessary so far. >> Kind Regards, >> Stefan > > Something fishy: > http/1.1: > +++ > > < HTTP/1.1 200 OK > < Date: Mon, 28 Mar 2022 13:48:23 GMT > < Server: Apache/2.5.1-dev (Unix) OpenSSL/1.1.1n > < Last-Modified: Fri, 25 Mar 2022 15:47:39 GMT > < ETag: "bf-5db0ce1e1e93e" > < Accept-Ranges: bytes > < Content-Length: 191 > < Content-Type: text/html > > +++ > http/2: > +++ > < HTTP/2 200 > < last-modified: Fri, 25 Mar 2022 15:47:39 GMT > < etag: "bf-5db0ce1e1e93e" > < accept-ranges: bytes > < content-length: 191 > < content-type: text/html > +++ > > Did I miss something? Just added the fix to the PR: *) core, mod_http1, mod_http: moved the handling of the standard response headers `Date` and `Server` from mod_http1 into the generic HTTP protocol handling. Response buckets not always carry those headers (values preserved from proxied responses), irregardless of the HTTP protocol versions involved. mod_http1: the serialization of response header into HTTP/1.x format always writes `Date` and `Server` first if present. This assured backward compatibility with clients who are accustomed to this order. Kind Regards, Stefan > > -- > Cheers > > Jean-Frederic >
