Skip to content

Fix bug where we send an extra newline character at the end of a multipa...#29

Closed
JonathanSmith wants to merge 1 commit intogoogleapis:masterfrom
JonathanSmith:master
Closed

Fix bug where we send an extra newline character at the end of a multipa...#29
JonathanSmith wants to merge 1 commit intogoogleapis:masterfrom
JonathanSmith:master

Conversation

@JonathanSmith
Copy link

As per.

http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html

There is only one newline/CRLF required before the final --boundary--, the second newline will be interpreted as data and appended to the payload.

I'm not sure if this is a platform specific issue as I have not tested this on windows. Perhaps it changes and should be a specific hex string for the newline delimiters?

@JonathanSmith
Copy link
Author

Associated issue here:
#28

@rakyll
Copy link
Contributor

rakyll commented Jul 23, 2014

Looks good.

Jonathan, did you sign Google's CLA? It's been explained on Contributing section (https://github.com/GoogleCloudPlatform/gcloud-node#contributing).

I can merge it once you sign it. Thanks.

@rakyll
Copy link
Contributor

rakyll commented Jul 25, 2014

Any news?

This bug is blocking our next release, I will need to contribute it myself :(

@JonathanSmith
Copy link
Author

Hi,
Sorry,

I've been working on getting the Corporate CLA signed by my company. I just poked our signature guy again so I'll let you know when it is signed/submitted, I hope they can get it back to me today. (If not, please don't let it block your release, as it is a very small change).

@rakyll
Copy link
Contributor

rakyll commented Jul 25, 2014

Yes, corporate CLAs might be an overkill for small changes. Let's wait until Monday. If we are not able to merge this, I'll author it.

@rakyll
Copy link
Contributor

rakyll commented Jul 29, 2014

Sent this change as 82544bb

@rakyll rakyll closed this Jul 29, 2014
chingor13 pushed a commit that referenced this pull request Aug 26, 2022
chingor13 pushed a commit that referenced this pull request Aug 26, 2022
chingor13 pushed a commit that referenced this pull request Sep 13, 2022
chingor13 pushed a commit that referenced this pull request Sep 13, 2022
sofisl pushed a commit that referenced this pull request Sep 15, 2022
sofisl pushed a commit that referenced this pull request Oct 12, 2022
* chore: lock files maintenance

* chore: lock files maintenance
sofisl pushed a commit that referenced this pull request Oct 13, 2022
sofisl pushed a commit that referenced this pull request Oct 13, 2022
sofisl pushed a commit that referenced this pull request Oct 13, 2022
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this pull request Oct 13, 2022
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
miguelvelezsa pushed a commit that referenced this pull request Jul 23, 2025
* Introduce ESLint.

Because ESLint does not support NodeJS 0.12.x, yet another script
is added to skip "npm run lint".

* Add eslintrc.yml
GautamSharda pushed a commit that referenced this pull request Jan 14, 2026
This is needed to fix the problem with the system tests on
CircleCI where the file specified by
GOOGLE_APPLICATION_CREDENTIALS could not be found.
GautamSharda pushed a commit that referenced this pull request Jan 15, 2026
This is needed to fix the problem with the system tests on
CircleCI where the file specified by
GOOGLE_APPLICATION_CREDENTIALS could not be found.
sofisl pushed a commit that referenced this pull request Jan 27, 2026
* The output from proto file compilation is now checked into the repo.
  The proto compile step does not need to be run on each compile/test.
  Instead we can regenerate the output files whenever the proto is
  updated. For this to work, we needed to ensure that the relative
  path to the generated files remains the same between compile time and
  runtime – these files are needed at both times.
* Reorganize the source code so that we no longer change the path
  relative to the root directory as part of the compilation process.
* TypeScript wants all source files to be in the `rootDir` which
  necessitated the move of third_party/types. Hopefully we can get rid
  of this file completely soon.
* Drop types/gcp-metadata-types.ts as gcp-metadata now ships with
  types.
* Drop third_party from package.json/files. Not sure why it needed to
  shipped.
* exclude build and proto directories from coverage
sofisl pushed a commit that referenced this pull request Jan 27, 2026
Coverage reporting regressed by #29 which added build/ to nyc.exclude
configuration.
sofisl pushed a commit that referenced this pull request Jan 27, 2026
* The output from proto file compilation is now checked into the repo.
  The proto compile step does not need to be run on each compile/test.
  Instead we can regenerate the output files whenever the proto is
  updated. For this to work, we needed to ensure that the relative
  path to the generated files remains the same between compile time and
  runtime – these files are needed at both times.
* Reorganize the source code so that we no longer change the path
  relative to the root directory as part of the compilation process.
* TypeScript wants all source files to be in the `rootDir` which
  necessitated the move of third_party/types. Hopefully we can get rid
  of this file completely soon.
* Drop types/gcp-metadata-types.ts as gcp-metadata now ships with
  types.
* Drop third_party from package.json/files. Not sure why it needed to
  shipped.
* exclude build and proto directories from coverage
sofisl pushed a commit that referenced this pull request Jan 27, 2026
Coverage reporting regressed by #29 which added build/ to nyc.exclude
configuration.
sofisl pushed a commit that referenced this pull request Feb 3, 2026
* Fix samples, upgrade repo-tools, and regenerate scaffolding.
GautamSharda pushed a commit that referenced this pull request Feb 5, 2026
This is needed to fix the problem with the system tests on
CircleCI where the file specified by
GOOGLE_APPLICATION_CREDENTIALS could not be found.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants