GitHub user wido opened a pull request:

    https://github.com/apache/cloudstack/pull/1341

    CLOUDSTACK-9238: Increase URL fields to 2048 charachters from 255

    255 characters is to small for various URLs like S3 pre-signed URLs.
    
    This causes one or more characters to be chopped of the end of the URL
    and this renders them useless.
    
    Internally in the code all URLs are passed as Strings and they are not
    sized limited. This was purely in the database.
    
    Other URL fields in the database were already 2048 characters.
    
    This limit was introduced in the 4.1 to 4.2 upgrade when Object storage
    like S3 and Swift was introduced in CloudStack for Secondary Storage.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/wido/cloudstack CLOUDSTACK-9238

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1341.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1341
    
----
commit a171bbc96dc4c44734d6c14265347f9db791a0cb
Author: Wido den Hollander <w...@widodh.nl>
Date:   2016-01-14T13:06:04Z

    CLOUDSTACK-9238: Increase URL fields to 2048 charachters from 255
    
    255 characters is to small for various URLs like S3 pre-signed URLs.
    
    This causes one or more characters to be chopped of the end of the URL
    and this renders them useless.
    
    Internally in the code all URLs are passed as Strings and they are not
    sized limited. This was purely in the database.
    
    Other URL fields in the database were already 2048 characters.
    
    This limit was introduced in the 4.1 to 4.2 upgrade when Object storage
    like S3 and Swift was introduced in CloudStack for Secondary Storage.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to