Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pushing a package with NuGet 3.4 causes a 500 error #2464

Closed
droyad opened this issue Apr 15, 2016 · 2 comments

Comments

@droyad
Copy link
Contributor

commented Apr 15, 2016

If the push command is used with NuGet 3.4 against the built in nuget feed, nuget will report Response status code does not indicate success: 500 (Internal Server Error). and the Octopus logs will show System.ArgumentException: Illegal characters in path.

This is due to a change in the Content-Disposition header to include a filename* property in addition to the filename property.

@droyad droyad added the kind/bug label Apr 15, 2016
@vanessalove vanessalove added the ready label Apr 25, 2016
@markryd markryd added in progress and removed ready labels Apr 29, 2016
@markryd markryd self-assigned this Apr 29, 2016
@markryd markryd closed this Apr 29, 2016
@markryd markryd removed the in progress label Apr 29, 2016
@markryd markryd added this to the 3.3.11 milestone Apr 29, 2016
@markryd

This comment has been minimized.

Copy link

commented Apr 29, 2016

We use Nancy's parsing of the header to get the filename. See https://github.com/NancyFx/Nancy/blob/master/src/Nancy/HttpMultipartBoundary.cs

Looks like there regex is looking for double quoted values, which aren't there anymore.

@lock

This comment has been minimized.

Copy link

commented Nov 26, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot unassigned markryd Nov 26, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Nov 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants
You can’t perform that action at this time.