Deploy packaged urlencoded

niko.dierickx's Avatar


12 Feb, 2018 09:06 AM

After upgrading to version 2018.02.01 the extractions of the packages are url-encoded what leads to issues in IIS.

What can we do to get old folder structure back

Extract from the log: (added spaces before and after @ cause otherwise it is recorgnized as an email)
09:06:02 Info | Deploying package: C:\Octopus\Files\Api @ S2.0.0+dev20180212.001 @ 8A875B173249AE4A9F64F33127626601.nupkg
09:06:04 Verbose | Extracting package to: C:\Octopus\Applications\Dev\Api\2.0.0%2Bdev20180212.001
09:06:27 Verbose | Extracted 170 files

Resulting dir structure:
 Directory of C:\Octopus\Applications\Dev\Api
09/02/2018 13:24 <DIR> 2.0.0%2Bdev20180209.003
09/02/2018 14:57 <DIR> 2.0.0%2Bdev20180209.003_1
09/02/2018 15:07 <DIR> 2.0.0%2Bdev20180209.004
09/02/2018 16:51 <DIR> 2.0.0%2Bdev20180209.005
12/02/2018 09:07 <DIR> 2.0.0%2Bdev20180212.001
09/02/2018 16:00 <DIR> 2.0.0+dev20180209.004

  1. Support Staff 1 Posted by Rob Erez on 12 Feb, 2018 10:35 PM

    Rob Erez's Avatar

    Hi Nikko,
    This change was a result of some updates made to support additional feeds where invalid filename characters are used in the packageIds. To facilitate those It was decided the most robust solution would be to encode the filenames to prevent any invalid characters getting used. This was calculated to be safer than trying to play a cat-and-mouse game finding and replacing characters on a case by case basis, and then dealing with issues of double encoding. Ill take a look at what can be done to preserve some of the "valid" characters which are getting transformed (in your case the +). This was added in a Breaking Changes section of the release notes In the meantime so I can understand the issue better, what is the reason you rely on specific folder names rather than just using the Octopus.Action.Package.InstallationDirectoryPath variable to configure as needed?

  2. 2 Posted by niko.dierickx on 13 Feb, 2018 06:42 AM

    niko.dierickx's Avatar

    Hi Rob,
    There is no specific reason why we did not use the Octopus.Action.Package.InstallationDirectoryPath variable, but until now it wasn’t needed, and the default path was considered a good location to map the IIS virtual directory to.
    The issue is that I don’t have an issue with the url-encodage itself, but IIS has. When we try to map a site to a folder with %2B in it, it breaks on us when trying to load the assemblies.
    The exact error message from IIS-Events is:
    Application Path: C:\Octopus\Applications\Dev\Api\2.0.0An unhandled exception has occurred.Bdev20180209.005\

    In the meantime, do you have an ETA on the fix where the + sign will be preserved?

    With Regards,

  3. Support Staff 3 Posted by Rob Erez on 14 Feb, 2018 04:08 AM

    Rob Erez's Avatar

    It is certainly strange that IIS is so picky about the file naming. I am looking at rolling out a fix that will allow valid filesystem characters like + which will hopefully be available in the next few days. Ill let you know once it is out. In the meantime is it possible to remove the metadata or use a custom installation directory? I know its not ideal but if you need these releases to go out immediately that should be a workable workaround. Thanks again,

  4. 4 Posted by c.p.yorke on 14 Feb, 2018 02:00 PM

    c.p.yorke's Avatar

    Hi Rob

    We have just fallen foul of this issue with IIS failing when the mapped folder has the %2b in it. We have just moved to a custom versioning convention for now but would like to move back to the SemVer + notation.

    Adding a +1 for the fix.


  5. Support Staff 5 Posted by Rob Erez on 15 Feb, 2018 09:38 PM

    Rob Erez's Avatar

    As an update, a fix will be going out in the next release (2018.3.4) which will allow the + characters in the file paths. This may be an interim fix until we can implement a more robust solution to allow for future cases when we may have other feeds which have illegal characters and need to work against IIS.
    Keep an eye out for this release in the next few days and let me know if you do (or don't) have any further problems.

  6. 6 Posted by c.p.yorke on 20 Feb, 2018 12:10 PM

    c.p.yorke's Avatar

    Hi Rob

    Just updated and deployed a release with the + symbol. All went well so I'm happy to confirm the fix is good for us.


  7. 7 Posted by niko.dierickx on 20 Feb, 2018 12:27 PM

    niko.dierickx's Avatar

    Hi Rob,

    I confirm that the fix is working for us too.
    Thank you very much for this quick fix, and keep up the good work.

    Niko Dierickx

  8. Support Staff 8 Posted by Rob Erez on 20 Feb, 2018 11:11 PM

    Rob Erez's Avatar

    Great to hear.
    Thanks for the update!

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac