(net.uri:uri-host (net.uri:parse-uri "http://test#"))

Defined a client-cache object that works with do-http-request to save HTTP responses and in the future use those saved responses rather than go out to the network to fetch responses.

Ensure that multiple users of the same cookie-jar do not interfere with each other.

When SSL was specified as T or a certificate, temporary redirect was performed correctly to https, but when specified with a context (as created via socket:make-ssl-client-context) object the redirection was incorrectly set to http. This patch ensures correct temporary redirection in all SSL cases.

parse-uri has been modified, for parsing the query of a URI, to not decode #+, #= and #& if they are percent encoded. This means %2b, for example, will not be converted to `+'. This is contrary to RFC 3986, but otherwise there is no way to pass these characters as field values.

parse-uri/render-uri and string-to-uri/uri-to-string are pairs which should be used together. Mixing usage on the same URI object will result in confusion.

• string-to-uri string:  Parse STRING as a URI and either signal an error if it cannot be parsed or return the URI object. This function differs from parse-uri in that the query is not decoded. The knowledge of how to properly decode the query is outside the bounds of RFC 3986.
• uri-to-string uri:  The inverse of string-to-uri, which returns the string representation of URI.

Non-strict parse allows #space in queries and double slashes at the start of the path are reduced to a single slash (http://foo.com//bar is parsed as http://foo.com/bar, in non-strict mode).

render-uri works in an upper-case modes.

merge-uris has been brought into conformance with RFC3986, mostly having to do with leading . and ..'s in path elements.

parse-uri no longer canonicalizes away a path of "/". That is, with this patch, this is no longer true:

(uri= (parse-uri "http://foo.com/") (parse-uri "http://foo.com"))

The CG patch (pjk007.001) and the IDE patch (pjl008.001) are both needed for the complete improvements.

If multiple windows have errors in their custom redisplay-window methods, confusion could result if the error for the first window is being handled and then a repaint message for the second window is handled. The error dialog may not appear or respond, and the IDE listener could be left unresponsive. On the GTK platforms, other windows could also fail to redraw, even after throwing out of the error. This patch corrects the problem.

• 3.1.0: Add the capability of making client server connections encrypted. See the :authenticate and :rsa-keys argumments to start-server and the :secure argument to open-network-database.
• 3.1.1: An expression cursor over a class will now be returned even if no member of the class has been created yet. The database must be read/write for this to work.

This patch changes the :ssl module to load dynamically linked OpenSSL libraries. As a result, OpenSSL updates will no longer require an ACL patch or update. This change will be transparent to many users of SSL, but some will need to modify their environment or their code to continue using SSL features.

If (require :ssl) signals openssl-load-error, then it will be necessary to specify the location of the OpenSSL shared libraries.

Most UNIX machines use the environment variable LD_LIBRARY_PATH to tell programs where to look for shared libraries. Mac OS X uses the variable DYLD_LIBRARY_PATH. Consult your operating system documentation for details on what you should use.

On Windows, this patch changes nothing. Note: the method of loading the SSL libraries has always been dynamic on Windows, but we have been the supplier of those binaries. See the readme.txt for more details on the binaries we distribute and how to use them.

In all cases, it is now the responsibility of the user to maintain a suitable set of OpenSSL shared libraries. In general, on machines with production software, those libraries will be part of operating system updates.

See the updated on-line documentation for details.

Windows users, please read the OpenSSL readme.txt for installation instructions.

Windows users, please read the OpenSSL readme.txt for installation instructions.

Windows users, please read the OpenSSL readme.txt for installation instructions.

Update to Aserve 1.3.26.

Make do-http-request merge the query part of the uri argument with any query parts specified using the :query keyword argument. Before the patch, the following call:

(net.aserve.client:do-http-request "http://localhost/xxx?q1=1"
         :query '(("q2" "2")))

Also, adds a new keyword argument ':ssl-args' to net.aserve:start, net.aserve.client:do-http-request, and net.aserve.client:make-http-client-request. As argument, it accepts a plist of keyword options and values accepted by make-ssl-client-stream or make-ssl-server-stream as pertains to the function being invoked. If :ssl-args is specified all other ssl related keyword arguments are ignored.

If a Java application connected and disconnected repeatedly from Lisp it was possible to signal errors, throw exceptions, or reach an unresponsive state in the Lisp server or the Java application. Connecting and disconnecting from separate threads in Java increased the likelihood of problems.

With this patch, the behavior of the Lisp server and Java client is much more robust when multiple connections are made repeatedly from the same Java client.

The recommended practice is to make connect and disconnect calls from the same thread. Calls to Lisp can be made safely from any thread. The state predicates released in a previous patch can be used to avoid exceptions thrown when calls are made in the wrong state.

Two unrelated fixes:

Fixes incorrect stack pointer alignments given in some hand-coded functions in the 32-bit Mac version, which causes some invocations of this lisp to die or hang when starting up or rebuilding during update.

Smp-related memory inconsistencies could cause the debugger to kill the lisp with a gc-failure message. This patch makes the debugger step around the problem.

Update the :ssl module to use OpenSSL 1.0.1f. Instructions on downloading the new OpenSSL binaries for Windows platforms can be found here

Revision (7001002) of the Jlinker Java library, implements new methods to query the state of a Jlinker connection. In a multi-threaded application, calls to Lisp from Java must be initiated after the connect() or advertise() call has completed the setup of a connection.

These changes apply mainly to applications running in socket mode. In native mode, the state is always READY.

The various call() methods in the LispCall class are modified to throw an IllegalStateException if a call is attempted in the wrong state.

See the updated jlinker documentation for further details.

net.post-office:send-letter's server argument can now be used to specify a program that does the delivery of the message. As in:

  (:program . "/usr/sbin/sendmail -t")

or

  (:program . ("/usr/sbin/sendmail" "-odq" "-t"))

The first form will invoke "/usr/sbin/sendmail -t" and pipe the message, constructed from the other arguments to send-letter, to the program. The second form will invoke excl:run-shell-command with this first argument:

  (vector "/usr/sbin/sendmail" "/usr/sbin/sendmail" "-odq" "-t")

which allows the program to be executed without an intermediate shell.