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

Server: EC2ws response header is missing #3

Closed
mumoshu opened this issue May 27, 2016 · 0 comments · Fixed by #4
Closed

Server: EC2ws response header is missing #3

mumoshu opened this issue May 27, 2016 · 0 comments · Fixed by #4

Comments

@mumoshu
Copy link
Contributor

mumoshu commented May 27, 2016

Hi, thanks for sharing this project :)

When I run curl --dump-header 169.254.169.254 on "actual" EC2 instances, I get:

$ curl --dump-header - http://169.254.169.254
HTTP/1.0 200 OK
Content-Type: text/plain
Accept-Ranges: bytes
ETag: "83579665"
Last-Modified: Thu, 19 May 2016 08:21:00 GMT
Content-Length: 153
Connection: close
Date: Fri, 27 May 2016 06:36:38 GMT
Server: EC2ws

*snip*

which includes the Server: EC2ws header.
Running the same curl command against aws-mock-metadata doesn't return it.

It may be a problem when you tried to use aws-mock-metadata to test applications that expect metadata service to return that header.
An example of such application is fluentd-plugin-google-cloud which relies on it to determine where it is running on(EC2 or GCE).

https://github.com/GoogleCloudPlatform/fluent-plugin-google-cloud/blob/b1db6ef/lib/fluent/plugin/out_google_cloud.rb#L507

mumoshu added a commit to mumoshu/aws-mock-metadata that referenced this issue May 27, 2016
@jtblin jtblin closed this as completed in #4 May 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant