Our partner is posting a notifikation to our server. When using Request.Form on the server there are no keys and not data at all.
When doing the same thing on localhost all data are populated just fine.
Were using IIS8.5 and Windows Server 2012.
It was caused by an http to an https redirection. When disabling this rule in an subdirectory it all worked.
Related
Please help :)
We have a web project. Frontend and backend. Windows Server 2019 IIS8
A problem is that we have a SSL certificate only for subdomain xxx.xxx.de (This we cant change)
Frontend work over https. Backend is on some server running, but we can not reach server over https.
Only over http.
Me idea was use Url Rewrite. That even works, but!!!
URL Rewrite Module has query string limit.
Anything over 3000 characters will be cut off!!
Does anyone know the problem?
Upd:
I made all settings for IIS for requestfilter over all maxlength and http sys in registery. If I only try over http, without url rewrite, then everything works with a 9000 byte query string. As soon as I turn on url rewrite, the query is cut off
There isn’t a query string limitation on URL rewrite module.
There are 2 related settings you can try:
Request filtering limitation and HTTP Runtime configuration.
HTTP.sys settings
Reference this official document: Http.sys registry settings for Windows - Internet Information Services | Microsoft Learn.
HTTP.sys can be configured by registry. You can create the following DWORD registry values under the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
I have a website hosted on a Windows Server that runs in IIS. I'm trying to do a GET request with Postman using the IP address of the server rather than the site URL.
Why does something this work: http://testsite.com/Callback?parameter=test
But this doesn't: http://{site IP address}/Callback?parameter=test
Try setting a Host: testsite.com header. The site might require that to work.
(if you can hit the URL in a web browser using the IP, then this isn't relevant)
Can you please check this setting in postman:
"Use Postman proxy" it should be set to No.
I use postman with this setting and localhost uri's work well for me..
I have 2 Windows 2012r2 Servers (Dev and Production) both running IIS 8. Both were configured identically as far I as know. I am in the process of installing wildcard certs on both of them.
I installed the cert on my Dev server and it's working. One thing that surprised me though was that I didn't have to add any additional bindings to any of my site configs (eg: I didn't add https/443) and just simply changing http to https in the browser is working, and showing the cert. Why is that?
My main question though is that on my Production server, before importing the wildcard cert, I tried simply changing the url for a couple of the domains I host from http to https in a browser to see what the result would be. When I do this I'm getting a redirect loop for all https tests. ???
I don't have any https URL Rewrites configured so I don't know what the cause of the redirect loop is. It does it for all sites on this server when trying to load it using https.
example:
http://mydomain.example.com (works)
https://mydomain.example.com (redirect loop)
Safari says, "...redirected you too many times. ERR_TOO_MANY_REDIRECTS"
Chrome says, "Too many redirects occurred..."
Additionally, if I load http://localhost on the server itself it works. If I load https://localhost I get an error, "Not Found - HTTP Error 404".
I should add that this Production server is behind an F5 Load Balancer so that could be playing into this behavior as well.
The cause of the redirect loop for all sites on the Production server was an irule on the F5 LB, that shouldn't have been there, that was looping port 443 back to itself. HTTPS for all sites worked after the irule was removed.
With regards to the Dev server and https sites working without having to add a binding. I also discovered that the F5 was configured to handle certs with a wildcard cert so local certs weren't even required. The data center team didn't communicate to me that the LB was configured to handle certs for these servers.
I am using Microsoft IIS to proxy requests for WebLogic server.
I've enabled https on IIS.
[http://webserver gives error that 'page must be viewed on https' and https://webserver gives content of Default.htm file]
I've enabled https on WebLogic Server.
[http://weblogic:7001/myapp/test.jsp and https://weblogic:7002/myapp/test.jsp both works]
Communication b/w IIS and WebLogic Server is on https.
The issue is when I access application on https using webserver URL (https://webserver/myapp/test.jsp) I do get response (content of test.jsp) but when I print request.getRequestURL() in a filter, I get http URL (http://webserver/myapp/test.jsp). This is causing a issue while doing sendRedirect()...
Why are my https URLs getting converted to http? Any idea?
Thanks.
Following solved my issue:
If a plug-in is communicating to WebLogic application server then do following –
Environments > Servers > select your server > General > Advanced > check WebLogic Plug-In Enabled
Thanks again.
URL rewriting has been done in my application which will act both as http and https according to the value passed to the page.
The extension that needs to be mapped has added to the IIS application mapping which was working fine in development environment.
But in testing site the http site is working fine where as https is not.
for ex: http://test1.com is working where as https://test1.com is not working
Can anyone tell me where i made mistake??
When a Java application connects to an SSL host it MUST be able to validate its signer.
but for doing self certificate it may face problem for you.
In case for validation use the SSLPoke class as i suggest. And if you cannot making a simple SSL socket connection for your server in a few lines of java then i will suggest you to use Paid-for certificate . Who's CA chain is probably validatable via the existing JRE certificate cacerts file.