The cause: When a relative url is used to specify the resource, java lang illegalargumentexception uri is not absolute is thrown. The whole url will be utilized to make the rest call in the spring boot RestTemplate.

Solution:

Solution 1: The relative url must be converted to an absolute url if it is let into the rest call in the RestTemplate. The absolute url will be used by the RestTemplate to locate the resource. The whole url “http:/localhost:8080/student” is being used to execute a rest call with RestTemplate in the example below.

package com.yawintutor;

import javax.servlet.http.HttpServletRequest;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;
import org.springframework.web.client.RestTemplate;

@RestController
public class TestController {

@GetMapping(value = "/student")
public Student getStudent() {
return new Student(1, "name1");
}

@GetMapping(value = "/getstudent")
private Student getStudentObject(HttpServletRequest request)
{
String uri = "http://localhost:8080/student";
RestTemplate restTemplate = new RestTemplate();
Student result = restTemplate.getForObject(uri, Student.class);
return result;
}
}

package com.yawintutor;

import javax.servlet.http.HttpServletRequest;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;
import org.springframework.web.client.RestTemplate;

@RestController
public class TestController {

@GetMapping(value = "/student")
public Student getStudent() {
return new Student(1, "name1");
}

@GetMapping(value = "/getstudent")
private Student getStudentObject(HttpServletRequest request)
{
String requestURL = request.getRequestURL().substring(0, request.getRequestURL().indexOf(request.getRequestURI()));
String uri = requestURL + "/student";
RestTemplate restTemplate = new RestTemplate();
Student result = restTemplate.getForObject(uri, Student.class);
return result;
}
}

external.server.url=http://www.yawintutor.com

package com.yawintutor;

import javax.servlet.http.HttpServletRequest;

import org.springframework.beans.factory.annotation.Value;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;
import org.springframework.web.client.RestTemplate;

@RestController
public class TestController {

@Value("${external.server.url}")
String externalServerURL;

@GetMapping(value = "/student")
public Student getStudent() {
return new Student(1, "name1");
}

@GetMapping(value = "/getstudent")
private Student getStudentObject()
{
String uri = externalServerURL + "/student";
RestTemplate restTemplate = new RestTemplate();
Student result = restTemplate.getForObject(uri, Student.class);
return result;
}
}

The cause: It results from the claimed library’s wrong location. Nvidia has changed the library’s location from the cuda-10.1 directory toward the cuda-10.2 directory. This is what would occur in Ubuntu 18.04 if Cuda was installed using a *.deb package from Nvidia.

Solution: 

To fix the error, include this path to the cuda-10.2 library in your LD_LIBRARY_PATH:

export LD_LIBRARY_PATH=/usr/local/cuda-10.2/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}

Hi. I will tell you the way to fix the hostname or IP not matching certificate’s altnames with Node.js.

Solution: 

You could utilize http-proxy with changeOrigin to true.

For example, I write:

const proxy = httpProxy.createProxyServer();

proxy.web(req, res, {
changeOrigin: true,
target: 'https://example.com:3000'
});

to set up a proxy so that traffic going to example.com:3000 is proxied.

Next, we design the server using:

httpProxy.createServer({
ssl: {
key: fs.readFileSync('valid-ssl-key.pem', 'utf8'),
cert: fs.readFileSync('valid-ssl-cert.pem', 'utf8')
},
target: 'https://example.com:3000',
secure: true
}).listen(443);

We use fs.readFileSync to read the key as well as certificate, and after that, we establish target to the hostname where our server is being hosted.

The cause: When you encounter the fatal error: unexpectedly found nil while unwrapping an optional value, you need to pay attention to that you forced open an optional with ! while it was nil.

Let’s assume that this code is capable of running even before the user has signed in. When a user is not logged in, the username field is null. As a result, it is optional.

Solution:

Solve the problem like this:

Before forcing the unwrapping of username, you use if-statement to see whether username is null. The code enclosed in the brackets { } is not run when username is nil.

let username:String? = nil

if username != nil {
let message = “Welcome, ” + username!
print(message)
}