Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Branch: master
Commits on Nov 6, 2014
  1. @capflam

    Fix FCGI worker when an error occures during the response streaming

    capflam authored
    When a FCGI server is called, the response can be streamed by the fcgi
    worker. Because yaws_cgi:fcgi_get_output/1 exits on error, if the exception is
    not catched, the client connection will wait for a quite long timeout to be
    closed.
Commits on Oct 16, 2014
  1. @vinoski

    Add SSL protocol_version configuration element

    vinoski authored
    Add protocol_version configuration element to allow supported protocols for
    SSL servers to be specified.
    
    Also add a new unit test for protocol_version.
  2. @vinoski
Commits on Sep 25, 2014
  1. @vinoski

    Fix #187: handle EINPROGRESS and EALREADY in sendfile driver

    vinoski authored
    Thanks to Maas-Maarten Zeeman for reporting this.
Commits on Sep 22, 2014
  1. @capflam

    Update known dialyzer warnings

    capflam authored
  2. @capflam
  3. @capflam
  4. @capflam
  5. @capflam
  6. @capflam

    Add 'honor_cipher_order' option in ssl part

    capflam authored
    This option can be used to set to true/false the 'honor_cipher_order' parameter
    on the ssl socket. This option was introduced in SSL application in Erlang/OTP
    17.0, so it will be ignored by Yaws for previous releases. When supported, this
    option is set by default to true.
  7. @klacke

    Merge branch 'klacke-yaws-log-fd-leak'

    klacke authored
    Fd leak
  8. @klacke

    Reloading the log could lead to an fd leak in the

    klacke authored
    case where we were having two servers on the same port,
    i.e both http and https
Commits on Sep 15, 2014
  1. @vinoski

    Fix yaws_sendfile to correctly handle non-latin1 filenames

    vinoski authored
    Fix a problem where a filename containing Chinese characters would cause
    yaws_sendfile to die in a list_to_binary call.
Commits on Sep 10, 2014
  1. @vinoski

    Exclude hipe application in reltool.config

    vinoski authored
    Several users have reported problems building releases using
    rel/reltool.config due to problems with hipe, so extend reltool.config to
    exclude hipe.
  2. @vinoski
  3. @vinoski
Commits on Aug 27, 2014
  1. @vinoski

    Merge pull request #183 from weisslj/ehtml-attribute-fixes

    vinoski authored
    EHTML: Fix small bug, allow binary attribute values and update documentation
Commits on Aug 26, 2014
  1. @vinoski

    Merge pull request #184 from weisslj/fix-build-without-pam

    vinoski authored
    Fix building without PAM (and small typo in configure help)
  2. @weisslj
  3. @weisslj

    Fix building without PAM

    weisslj authored
    Fixes this error in `make`:
    
        /usr/bin/install: cannot stat ‘epam’: No such file or directory
        make[1]: *** [post-build] Error 1
Commits on Aug 25, 2014
  1. @weisslj
  2. @weisslj

    yaws_api: Allow binary attribute values in ehtml

    weisslj authored
    Binary attribute values are already supported in exhtml.
  3. @weisslj

    yaws_api: Fix ehtml {check, _, number()} attributes

    weisslj authored
    Attribute {check, Key, 10} should expand the same way as {Key, 10}.
  4. @weisslj
Commits on Aug 20, 2014
  1. @weisslj

    yaws_api: Make end tags HTML5-compatible in ehtml_expand

    weisslj authored
    Currently, HTML generated by Yaws ehtml does not validate correctly as
    HTML5 (e.g. using http://validator.w3.org/). The reason is that in HTML5
    "void elements" like <br> must not have a closing end tag:
    
    Forbidden: <br></br>
    Allowed: <br>
    Allowed (and also valid XHTML): <br />
    
    Also, since the self-closing tag syntax ("/>") is simply ignored in
    HTML5, some elements must have an end tag:
    
    Forbidden: <p />
    Allowed: <p></p>
    
    This patch fixes both issues and also adds tests.
    
    References:
    - http://stackoverflow.com/questions/10598501/closing-tags-in-html5
    - http://stackoverflow.com/questions/1946426/html-5-is-it-br-br-or-br
    - http://www.w3.org/TR/html-markup/syntax.html#void-element
Commits on Jul 24, 2014
  1. @capflam

    Use iolist_to_binary/iolist_size instead of custom functions

    capflam authored
    And avoid some useless conversions
Commits on Jul 23, 2014
  1. @vinoski

    Merge pull request #180 from yakaz/fix-contenttype-matching-in-yaws_api

    vinoski authored
    yaws_api: Fix matching of Content-Type in `parse_post/1`
  2. @dumbbell

    yaws_api: Fix matching of Content-Type in parse_post/1

    dumbbell authored
    "application/x-www-form-urlencoded" can be followed by attributes, such
    as "; charset=UTF-8".
Commits on Jul 21, 2014
  1. @capflam

    Update known dialyzer warnings

    capflam authored
  2. @capflam

    Split content data of FCGI records to be compliant with the spec

    capflam authored
    According to the FCGI specification, the size of the content data should be
    lesser or equal to 65535.
    See http://www.fastcgi.com/drupal/node/6?q=node/22#S3.3 for details.
Commits on Jul 10, 2014
  1. @capflam

    Remove support of wildcards for R15B03 and previous

    capflam authored
    A bug in filelib:wildcard/1,2 was fixed in R16B:
      erlang/otp@70b5e24
    
    So, wildcard strings in the configuration file are now forbidden for older
    releases.
  2. @capflam
  3. @capflam

    Add support of wildcards and relative paths to load sub-config files.

    capflam authored
    Now, subconfig and subconfigdir targets accept relative paths, searched
    relatively to the configuration location. So for the configuration
    "/etc/yaws/yaws.conf", all relative files and directories will be searched from
    "/etc/yaws". Of course, absolute paths are always supported.
    
    furthermore, the subconfig target can take Unix-style wildcard strings to
    include several files at once. See filelib:wildcard/1 for details.
    
    Last, hidden files, starting by a dot, will be ignored in any cases.
  4. @capflam

    Check #deflate.min_compress_size option for large files

    capflam authored
    Now large files are compressed only if their size is greater than
    the #deflate.min_compress_size option.
  5. @capflam

    Relax rules that allow the parsing of a query string or an urlencoded…

    capflam authored
    … body
    
    The parsing of a query string or an urlencoded body was allowed, respectively,
    for 'GET' or 'POST' requests. Now, this can be done for any kind of requests. Of
    course, a body is parsed only if its Content-Type is set to
    'x-www-form-urlencoded'.
    
    In the same way, a body can now be parsed as a multipart content if its
    Content-Type is set to 'multipart/form-data', regardless of the request type.
    
    As a consequence of these changes, yaws_api:getvar/2 now returns the merged
    result of values found in the query string and in the urlencoded body (if any).
Something went wrong with that request. Please try again.