One can specify which proxy requests are permitted or refused by using a proxy-control object. One can also add methods to the authorize-proxy-request generic function to further control the authorization process.

Updated documentation on AllegroServe's proxy feature is available here

This document shows a table of environment variables. The values of these environment variables previously had to be either base 16 or base 10 numbers. They can now be numbers followed by a multiplier, which are:

• k or K: multiply by 1024
• m or M: multiply by (1024 * 1024)

• Improve Perl comatibility with split-re. These changes are described here.
• Nested bound repetitions causing either errors on parsing or infinite loops during execution.
• A specific nested alternation pattern to get into infinite loop.

• This patch introduces several special variables in Lisp and static fields in Java to control how long some socket operations should last:
  • *jlinker-read-timeout*, LispCall.readTimeout:  This number limits how long a single socket read operation can block an application. The initial value is 30 seconds. This timeout can be used to detect network failures.
  • *jlinker-reply-timeout*, LispCall.replyTimeout:  This number limits how long a complete call can tie up the interface. The initial value in Lisp is 30 seconds, in Java it is 300 seconds.
  • *jlinker-request-timeout*, LispCall.requestTimeout:  This number specifies how long each side will wait for a new call from the other side. The initial value is nil in Lisp and 0 in Java to specify an indefinite wait.
• refines the search for a Java runtime in both Windows and Unix environments to reduce the need for applications to specify a value for *jlinker-java-home*.
• corrects a problem in the native interface to allow events registered with jregister-handler to be called correctly from Java.
• corrects a problem in the native interface to allow functions with zero arguments to be called from Java.
• includes a new Java jar file. This new jar file is needed if the new features are required. Applications that do not need the new features can continue to run with the original jar file distributed with ACL 9.0.

The code generator in the SOAP module was making an incorrect assumption about the format of some WSDL definitions. As a result, a no-applicable-method error was signalled when generating client code from some WSDL definitions. The patch corrects the assumption and avoids the inappropriate error signal.

The client code generator was generating an incorrect Lisp representation from a pattern such as <complex><choice>...</choice></complex> in a WSDL definition. As a result, arguments passed to a generated client function were ignored. The patch corrects the generated Lisp type definition, and the arguments are now correctly inserted in the client message.

The function parse-to-lxml is augmented with two new keyword arguments:

• comments: When t collect XML comments into the LXML output as (:comment string) entries. When nil, comments are discarded. Default is nil.
• warn: This argument is propagated to the SAX parser.

The function is also modified to collect processing instructions in the XML document into the LXML output as (:pi target data) entries.

If the :normalize argument to parse-to-lxml is one of the keywords :trim-simple, :trim-complex, :trim-all, or :trim, the parser will remove some whitespace characters that normally clutter the LXML output. This non-standard behavior is added as an optional convenience feature. Read the full details in the documentation page for parse-to-lxml.

Encoding a double-float zero was signalling an error. This patch causes double-float zero to be encoded correctly.

Allow collapsible whitespace in boolean element content.

Several minor enhancements:

• xmp-redef-default:  NEW variable in net.xmp.soap. The value of this variable defines the default value of the :redef keyword argument to define-soap-type and define-soap-element. The inital setting is :warn; other possible values are nil and :error.
• xmp-report-error-action:  NEW variable in net.xmp.soap. The value of this variable defines the behavior when an error occurs in a user-supplied :include or :import action in a call to decode-wsdl-*. The initial value is :warn to signal a warning but continue decoding the wsdl. Other values are :ignore to ignore errors silently, or :error to signal an error.
• decode-wsdl-at-uri:  The uri argument can be a string, a uri instance or a list of args to do-http-request.

Do not canonicalize a null fragment away. That is, the following URIs are now distinct:

• http://www.example.com/path#
• http://www.example.com/path