Commits on Feb 18, 2011
  1. @dklayer

    rfe10416: tweak warn text, turn into 'note'

    Can't warn here because it will kill the ACL build (which
    stops for warnings).  Also, the best thing is to pass on the text
    of the condition, rather than a canned message.
    Change-Id: I3d05265bc587a79c847ce4940f87f59184310875
    dklayer committed Feb 17, 2011
  2. @marijnh

    Make the check for 100-continue header less fragile.

    Using equal directly causes problem when there is other stuff in the
    expect: header. This was causing trouble in AllegroGraph. The code now
    uses a regexp to look for 100-continue.
    marijnh committed with John Foderaro Feb 4, 2011
Commits on Feb 17, 2011
  1. rfe10416: add compression

    Support server gzip like compressing body before sending to client.
    Support client gzip like uncompressing body as sent from server.
    Are there user visible changes in this commit?  yes
    Is bootstrapping needed?   no
    Are tests included for new features?  yes
    Tests run:  t-aserve
    rfe10416 - enable compression
    aserve can now compress responses on the fly if request.
    aserve's client code can request a compressed transfer and can
    uncompress the result.
    See documentation for API changes.
    Subsequent releases will increase aserve's capability to cover
    static file transfers.
    rfe10416 - enable compression
    (do-http-request &key compress)
     takes a :compress argument (default nil) which if true causes
     the request to the server to include an 'Accept-Encoding: gzip'
     header line.  The server then may choose to return the result
     compressed to the client which will then uncompress it before
     returning the body from do-http-request.
    (start &key compress)
    The net.aserve:start function takes a :compress argument.  The value
    of this argument is is stored in the enable-compression slot of
    the wserver object.  The default value of this argument is
    true if the deflate module was successfully loaded.
    The enable-compression slot of the wserver object is a server wide
    control on whether the server will compress a result before
    sending it back.  If this slot has the value nil then under no
    cicumstance will the server compress a value before returning it.
    If the value is true then the server may or may not compress a
    result before sending it to the client.
    (publish-xxx  &key compress )
    Each entity has a compress slot as well, set by the
    compress argument of the various publish functions.  The default for
    the :compress argument for all publish functions is true.
    Furthermore the compute-strategy generic function that determines
    how a result will be returned is the function that decides if
    compression will be done.
    At the present time (with changes planned for the future) the only
    entity that can be compressed is the computed entity. In order
    for compression to occur a number of things must be true
    1. the enable-compression slot of the wserver object must be true
    2. the compress slot of the entity must be true
    3. the entity must be a computed entity (for now)
    4. the client must state that it can accept gzip content-encoding
    compression will work with any combination of chunking and/or ssl.
    Change-Id: I683ff58a12447b8614263cafce5990ee491ed387
    John Foderaro committed Feb 17, 2011
Commits on Feb 16, 2011
  1. rfe8891: support chunking with ssl

    http/1.1 clients and servers prefer to send and receive
    data using chunking.  This change allows Aserve to support
    chunking in the client and server if the connection is ssl
    Are there user visible changes in this commit?  yes
    Is bootstrapping needed?   no
    Are tests included for new features?  no, existing tests test new features
    Tests run:  t-aserve
    rfe8891: support chunking with ssl
    In the past AllegoServe disabled chunking for an ssl server
    and told users to use the http/1.0 protocol for clients when
    ssl was being used.  Now those restrictions are gone.
    The default for the server will be to use chunking in all
    cases and clients can specify http/1.1 for requests over ssl.
    just a note to the documentation editor to look for references
    to chunking and ssl in the manual and remove the text.
    Change-Id: Id2c2b2e34c1e49c8bfc14f0eb31122d21afa41cc
    John Foderaro committed Feb 16, 2011
Commits on Feb 15, 2011
  1. restore code to coding standards

    A few code snippets had been added that did not conform
    to the coding standard promised in the header. These
    were updated. No functional changes were made.
    Are there user visible changes in this commit?  yes/no
    Is bootstrapping needed?   no
    Are tests included for new features?  no new features
    Tests run:  t-aserve
    Change-Id: Idddb093e0b8d94fca87170698992a4f18b641508
    John Foderaro committed Feb 13, 2011
Commits on Feb 14, 2011
  1. Support :connect method requests in do-http-request

    Properly handle :connect method requests in do-http-request.
    CONNECT requests differ slightly from all other request types in that
    they MUST be passed through a proxy, and the value passed on the
    Request-Line of the message is an Authority (host:port) instead of a
    valid URI.
    changes to keep-alive and skip-body semantics in do-http-request.
    Other changes in make-client-http-request.
    Are there user visible changes in this commit?  no
    Are tests included for new features?  no new features
    Tests run:  none
    Change-Id: I89f5157782a573b5e96e9281fd7b49fa24e47490
    Mikel Bancroft committed Feb 14, 2011
Commits on Feb 10, 2011
  1. @dklayer

    v1.2.71: Print "flush session #" information during debugging only.

    Version bumped by layer.
    Elliott Johnson committed with dklayer Feb 9, 2011
Commits on Jan 13, 2011
  1. remove .cvsignore files

    Kevin Layer committed Jan 12, 2011
Commits on Dec 8, 2010
Commits on Nov 15, 2010
  1. @dklayer

    require :autozoom for top-level.debug package

    This module was implicitly loaded, so this just makes it explicit.  It
    also makes aserve buildable after bug19841 is fixed.
    Change-Id: Id23f40204d6f4b0e1fa50ae02451f184c96ca4c6
    dklayer committed Nov 15, 2010
Commits on Oct 15, 2010
  1. @dklayer

    Remove ChangeLog's from *aserve-other-files*

    Change-Id: I1c02d35c0f58f798695ecff7bc25c470b2442186
    dklayer committed Oct 15, 2010
  2. @dklayer

    Update defpatch for ACL 8.2 aserve.004

    Change-Id: Ie8016cdd329f8ce6b718963c4475c71b9a2e3f01
    dklayer committed Oct 15, 2010
  3. @marijnh

    Add support for Expect: 100-continue requests

    aserve version: 1.2.70
    The HTTP spec specifies that a client who does not want to send its
    body before the server has confirmed that it is prepared to read it
    can send an Expect: 100-continue header. The server then sends a
    response with a 100 status code, after which the client sends its
    body, and things continue as normal.
    We have two concrete uses for this:
     1) Curl sends such a header before sending any big body. It will then
        wait for a while before sending its body anyway. This means that,
        by default, curl works with our server, but is much slower than it
        has to be for big requests. We have a work-around of specifying -H
        "Expect:", but it would be better if things just worked.
     2) The proxy used between the AG front and backend can't reliably use
        keep-alive when forwarding PUT or POST requests without this
        feature. If it forwards a request body, and the socket it was
        using turned out to be stale, it no longer has the body, and the
        request fails. It can send Expect: 100-continue as a way to test
        whether the server is still listening on the socket it has, before
        actually forwarding the body.
    Change-Id: Ibd6c5b3c54883aac0681a577a02cf3d9a750a621
    marijnh committed with John Foderaro Oct 13, 2010
Commits on Oct 6, 2010
  1. update version to 1.2.69

    Change-Id: I351a38c88998d7c07987e482b6a456800ffe2980
    John Foderaro committed Oct 6, 2010
  2. @dklayer

    Update defpatch for 8.2 to v3, aserve 1.2.69

    Change-Id: Ic28f58e163ea4cf8590806dd9e6446e02747eafb
    dklayer committed Oct 6, 2010
  3. @marijnh @dklayer

    rfe10129: Make logging though method specialized on wserver class

    This centralizes logmess and brief-logmess to both send their message
    through a log-for-wserver method, which is specialized on the default
    wserver class. This allows client software to log in a different way
    by using its own wserver class.
    now AllegroServe version 1.2.69
    Change-Id: I9cd37da6f693211e44e45fd1119056f3d6e44812
    marijnh committed with dklayer Oct 5, 2010
Commits on Aug 11, 2010
  1. @dklayer

    update defpatch for 1.2.68 patch

    Change-Id: I3b9e8ac08c9b1586a3fe3f583f223f41944f9e2e
    dklayer committed Aug 11, 2010
Commits on Aug 10, 2010
  1. @dklayer

    obey keep-alive requests for PUT and POST requests. Aserve version 1.…

    see bug19575
    Change-Id: Ica3f7882e4b3e76c722262d61e3881ac71605425
    John Foderaro committed with dklayer Aug 10, 2010
Commits on Jul 7, 2010
  1. @dklayer

    bump version to 1.2.67, defpatch for 8.2

    Change-Id: I1c224cdc24a8e308fe62889c5c6c0ca5b1b95fe3
    dklayer committed Jul 7, 2010
  2. @dklayer

    Support persistent connections (keep-alive) in aserve client

    Calls to do-http-request can now specify :keep-alive t and
    do-http-request will return the socket connected to the server if
    the server agrees with the request. That socket connection can be
    used in subsequent calls to do-http-request.
    Are there user visible changes in this commit?  yes
    Is bootstrapping needed?   no
    Are tests included for new features?  yes (in
    Tests run:  aserve/test/t-aserve
    rfe9811 - the :keep-alive arguement to do-http-request will now
    cause do-http-request to return a fifth value: a socket connected
    to the server.  That fifth value will be nil if the server refuses
    to keep the connection with the client open.   Even if the server
    agrees to keeps the connection alive it will close it after some
    period of inactivity.
    do-http-request takes a :connection argument which is how the
    socket returned by do-http-request should be passed to the
    next do-http-request call.  It is ok if the value of
    the :connection argument is nil or closed socket.  do-http-request
    will notice that the socket is unusable and will create a new one.
    rfe9811 has the documention changes
    Change-Id: Ife1f8a9b7f0a4ba3377750c08534251e7a62aad6
    John Foderaro committed with dklayer Jul 7, 2010
Commits on Apr 23, 2010
  1. @dklayer

    rfe9550: ASDF integration

    Contributed by james anderson <>.
    dklayer committed Apr 23, 2010
Commits on Mar 26, 2010
  1. @dklayer

    ChangeLog is obsolete

    dklayer committed Mar 26, 2010
  2. @dklayer

    ChangeLog is now obsolete

    dklayer committed Mar 26, 2010
Commits on Mar 23, 2010
  1. @dklayer

    time the loading of

    dklayer committed Mar 23, 2010
Commits on Feb 3, 2010
  1. @dklayer
  2. Clean Changelog, bump version

    Robert Rorschach committed Feb 3, 2010
Commits on Jan 28, 2010
  1. retrofit for 7.0-8.1

    2010-01-28  Robert Rorschach  <>
    	* retrofit for 7.0-8.1
    	* retrofit for 7.0-8.1
    Robert Rorschach committed Jan 28, 2010
Commits on Jan 22, 2010
  1. resolve conflicts

    Robert Rorschach committed Jan 22, 2010
Commits on Jan 21, 2010
  1. prealpha checkpoint

    2010-01-21  Robert Rorschach  <>
    	* smp changes
    Robert Rorschach committed Jan 21, 2010
Commits on Nov 9, 2009
  1. @dklayer

    don't do an 8.2.beta patch

    dklayer committed Nov 9, 2009
  2. @dklayer
Commits on Nov 1, 2009
  1. @marijnh

    allow HTTP 1.1 connections to be persistent as long as no connection:…

    … close is sent (rather than only when connection: keep-alive is sent)
    marijnh committed Nov 1, 2009
Commits on Oct 21, 2009
  1. resolve conflicts

    Robert Rorschach committed Oct 21, 2009
Commits on Oct 15, 2009
  1. @dklayer
Commits on Oct 14, 2009
  1. @marijnh