I am trying to connect to an https endpoint by creating a soapui project. I do not have to make any changes in my soapui project to connect on https. Not done any configurations for TLS. Not done any keystore configs. The https request still goes through and returns data.
However, if I try to call the https endpoint from my code (Mulesoft webservice consumer) it tries to find the certificate.
Is there some default configuration for soapui that makes this thing happen ?
Thanks.
Thanks for your replies. I did get a resolution long back but was too busy with project deadlines to update the answer here.
Yes, Some headers that SOAPUI passed along with the request that I was not aware of. When I looked at the raw request it was clear.
Related
I have a web api application built with yarp support listening on port 443.
I know it is up and running because postman says so when https://myserver/info. 'Info' is a simple http GET returning some strings from a simple controller.
I also have a web api project listening on port 5002 which I know is functioning because postman says so when https://myserver:5002/myotherapp/info.
I would like postman to tell me that https://myserver/myotherapp/info is also valid, but have not been able to configure it so.
I have tried numerous different combinations in the appsettings.json to achieve this but to no avail. All I am trying to do is direct to localhost:5002 on the server. In my current setup I am seeing 503 Service Unavailable in postman.
It may not be a configuration issue but could someone assist me by confirming what the ReverseProxy element of appsettings.json should look like in this simplest of cases?
I am trying to build a system using Socket.io and YARP. Yarp is functioning has a Reverse Proxy to all my Services.
When trying establish a connection to my socket.io service, through yarp, I am getting connection_error:
I noticed there are proper configurations used in other Reversed Proxy solutions that are well documented in Socket.io website:
https://socket.io/docs/v4/reverse-proxy/
However, I can't "translate" what they are doing to YARP. Does anyone know if this is possible?
Thanks in advance
I guess stackoverflow was my rubberduck this time...
I checked in postman the request that was being made through my Yarp Server and turns out it wasn't even hitting the correct path. For yarp to connect to a socket.io server you have to use this kind of path in your configuration file:
It seems that a sokcetio request uses it's own path, so you have to make your reverse proxy match the beggining "socket.io/"
I set up an API Gateway through Gravitee.io and a Springboot application, and everything seems to work fine as per the rest endpoints, running in https also.
Now, I would like to open a websocket connection through the same port (8080), but when the client tries to do it, this error come up server-side:
Handshake failed due to invalid Upgrade header: null
Looking for some solutions online, seems like a port issue, which could be potentially easy to manage with a tomcat server. But there is a way to address this issue using Gravitee.io ?
Thanks
I would advice you to create an issue in gravitee.io repository at https://github.com/gravitee-io/issues/issues/new
Websocket is not yet ready within Gravitee.io
there doesn't seem to exist any configuration that enables HTTPS only access to neo4j databases.
I've tried disabling the HTTP connectors but neo4j needs at least one HTTP connector otherwise it wouldn't start the service at all.
I found that commenting out the HTTP connector would let the neo4j service start but triggers an error in all browsers except chrome that wouldn't let you connect to the database.
As far as my research has brought me. There is no neo4j-only solution to this problem at the moment.
From what I've read and found out there might be several possibilities like limiting http access to port 7474 from outside of your network and redirecting http to https.
I was not able to test them personally but it seems that there's no different way to do this.
For now http has to be enabled and configured for https to work.
I am using Spring Boot v1.1.9.RELEASE and I deploy my app to Heroku. I have just added an SSL certificate and it works fine, if I manually change the URL to HTTPS.
The problem is that after login, Spring Security switches back to HTTP. I've read-up on this and found that adding the following forces HTTPS for all requests which sounds like exactly what I want:
.and().requiresChannel().anyRequest().requiresSecure()
However, when I try this, I get a redirect loop error. I don't understand why the server would constantly redirect. I want every request to be HTTPS. So the above code tells the server to redirect to HTTPS if the request is HTTP which seems to work. But then it retries the redirect over and over. Does anyone know why it does this? The logs don't seem to be providing any insight into the behaviour.
Note: I also read somewhere that port-mapping may be the culprit but the suggested solution was to set a port mapping of 80 to 443 which as far as I know is the default setting. I tried it anyway and it made no difference.
The most likely reason is that the HTTPS connection is not terminated at the servlet container and the container is unable to differentiate between connections which are over HTTPS or HTTP.
Check whether the isSecure method on HttpServletRequest returns true when you make a request over HTTPS. If it doesn't then you need to find some way of configuring a Heroku application to allow the container to tell the difference. Most likely the router will set a header such as HTTP_X_FORWARDED_PROTO which the container can be configured to make use of. You can do this in tomcat using the RemoteIpValve but I don't know how much control you have over this in Heroku.
In Spring Boot the usage of the Forwarded-Headers (RFC 7239) can be activated in application.properties:
server.forward-headers-strategy=native
Reference: Spring Boot Documentation