image-service | 图床服务。提供多版本图片转换。

A quick fix would be to add a 'depends_on' clause so that the api-service depends on the config server - that way the api-service won't start until the config server is up.

As per spring docs you can send Headers from zuul to other services with the help of zuul configuration.

Spring Docs:

The sensitiveHeaders are a blacklist, and the default is not empty. Consequently, to make Zuul send all headers (except the ignored ones), you must explicitly set it to the empty list. Doing so is necessary if you want to pass cookie or authorization headers to your back end.

Example:

I faced the same issue with a get request. You need to pass headers in axios properties. axios.get(url, { cancelToken: ..., headers: { ... } }).then...

By default, the Maven Surefire plugin (responsible for running unit tests in the test phase) recognizes classes called *Test. The Maven Failsafe plugin (responsible for running integration tests in the integration-test phase) recognizes classes called *IT.

Your test class is called AdRestServiceTest, which would be executed in the test phase. You want it to be executed in the integration-test phase, because it's the integration-test phase that is surrounded by pre-integration-test and post-integration-test phases.

So you need to rename AdRestServiceTest to AdRestServiceIT. (Another option would be to reconfigure the Surefire and Failsafe plugins.)

You have two options:

1. Stop using */* as the type selector. This is treating everything as binary, and therefore base64 encoding everything. Unfortunately, you can't express an exception to the rule, only things that follow the rule. You could add a comprehensive list of the types that must be treated as binary, but that sounds fragile to me.

2. Just accept the base64 JSON and de-base64 it on the other side. This seems easiest. You're using node, it looks like, and there are ample tutorials about this. Sure, it adds some steps and a bit of bloat, but let's be honest, you're using API Gateway and Lambda (which are nice tools, but...) so clearly performance doesn't have to be tuned to the millisecond here.

1. Hit the server url separately in browser and see if you get the expected response. If this is okay, then the problem is with the client.

2. On seeing your client code, one issue seems obvious. You are not using the observable from ImageServiceService properly. All your manipulations should be within the subscribe method.

   onSubmit(image: string) { this.imageService.getImages(image).subscribe(response => { this.data = response; console.log(this.data.length); // Do other manipulations that you wish to do }); }

3. If you using the observable to display something in the view, then consider . using async pipe

Try this package. It should work for what you want to accomplish.

Edit:

Your slideshow could look something more like this, which is more modular and cleaner:

Turns out it was exceptionally easy.

I already had built the tool that makes the request to the external API inside my network for the image. Calling the API returns 2 important things: the raw image data and the mime type.

All I had to do was pass these through rails.

The controller action ended up looking like this