I am getting HTTP 400 error in our application.The error is coming frequently but some times we are able to access application without 400.
There is one SSO application in which our application's link is added so same session details we are getting in our application.But when i login to the other application from same domain, and refresh the first one, I get HTTP 400 error. other applications cookies are also getting in our application.
I am using apache 2.2 on web server and tomcat 7 on app server.
I have tried increasing LimitRequestFieldSize on web server but it didn't work and current LimitRequestFieldSize is 65535.
Technology stack :- backend :- Java,Documentum
apache 2.2 web server tomcat 7 on app server
Kindly check and provide solution it will be helpful.
Thanks in advance.
Related
I have a web application running on .Net Core 2.2 and so far it has been deployed on various servers on IIS
screenshot of web.config
The cookies created on all the servers so far are around 2.7kb
screenshot of usual behavior - localhost
screenshot of usual behavior - public domain with htps
When deployed on a particular server that cookie becomes too large and is chunked. Causing problems overall screenshot of chunked cookie
Does anyone know what is causing this?
I have built a RESTful API in which I set the http_response_code() in some cases. I was using the XAMPP APACHE web server while developing the API on localhost.
The problem is that, now that I have deployed the API on our EC2 containerized DEV instance, which runs an nginx web server, all of my http_response_code() calls are not working and the API is always returning a "200 OK" status code, which is not wanted in cases like an error should be thrown when for example a user already exists in the system and a registration with the same email is forbidden.
Therefore, is there an equivalent of http_response_code() for nginx web servers?
HTTP Error 502.3 - Bad Gateway
There was a connection error while trying to route the request.
Most likely causes:
•The CGI application did not return a valid set of HTTP errors.
•A server acting as a proxy or gateway was unable to process the request due to an error in a parent gateway.
Things you can try:
•Use DebugDiag to troubleshoot the CGI application.
•Determine if a proxy or gateway is responsible for this error.
Detailed Error Information:
Module
AspNetCoreModule
Notification
ExecuteRequestHandler
Handler
aspNetCore
Error Code
0x8007000d
Requested URL
http://localhost:15536/
Physical Path
C:\Users\HenryP\Desktop\NopCommerce_4.2.0\src\Presentation\Nop.Web
Logon Method
Anonymous
Login User
Anonymous
More Information:
This error occurs when a CGI application does not return a valid set of HTTP headers, or when a proxy or gateway was unable to send the request to a parent gateway. You may need to get a network trace or contact the proxy server administrator if it is not a CGI problem.
View more information »
It seems this is not CGI issue. Newest nopCommerce version run on .net core version and require Full Trust. And my experience used Godaddy in the past that they didn't support Full Trust, so you can't install nopCommerce on their platform. You better contact their support team or you can ask this issue on nopCommerce forum. But, it seeems that nopCommerce can't run well on Godaddy platform. If you use nopCommerce, I recommend you can check Asphostportal.
According to your description, this is a generic error for when IIS can't find the specified .NET Core components ,and doesn't know where to forward requests.So i suggest you to check once you select asp.net or asp.net core while creating your site
I have a web application that has built on ASP.NET CORE 3. This web application uses asp.net core 3 web api. Everything works fine. But problem starts when I move them to the staging server. Web Application was not able to connect web api. They both hosted on same machine but have different port.
For example :
Web Application URL http://52.X.X.X:94/MyWeb
Web API URL http://52.X.X.X:91/MyWebAPI
I get following error
System.Net.Http.HttpRequestException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
I have enabled CORS in web API.
However, If I move Web Api to Port 80 (http://52.X.X.X:80/MyWebApi ) then everything is working.
On my local IIS they both are working.On local IIS they were published on same port ( 94 and 91 respectively)
Can anyone tell what I am missing?
do you have appropriate web.config on server? compare local web.config with server web.config. maybe you missed some part like kestler or something else.
if it's alright, then check your webapi with postman, maybe webapi didn't published correctly.
I receive the following error when I attempt to make a web request to a recently deployed remote server that's shared and running IIS:
SEC7120: Origin http://localhost:8000 not found in
Access-Control-Allow-Origin header.
HTTP404: NOT FOUND - The server has not found anything matching the
requested URI (Uniform Resource Identifier). (XHR)GET -
http://mywebsite/someservice/somevalue
All of this works fine when I run the web server on my local machine.
Any suggestions?
You'll need to set up CORS handling on the server so that browsers will allow cross-origin javascript requests. See Enabling Cross-Origin Requests (CORS) for instructions on how to do this for .Net Core apps.