Since I migrated my app (but its just a blank project for now) when I try to access the admin login page, I have issues both with Chrome & Firefox. On Chrome, messages are :
GET https://myapp/filament/assets/app.css?id=74b0e5d1ac0bd5c2e7700a3ab38b4202 net::ERR_HTTP2_PROTOCOL_ERROR 200
GET https://myapp/filament/assets/app.js?id=a89643d28638f3978429678585b1ce2d net::ERR_HTTP2_PROTOCOL_ERROR 200
No issue when in http only. Any advice ?
Thx a lot
tried both http and https on local and distant (prod) server.
tried on several Navigators (chrome & firefox)
Related
I am trying out maildev for sending emails project on a spring boot project. I have successfully installed maildev and I am able to start the mail server successfully as shown below[
When i serch http://0.0.0.0:1080 in the browser i get "...It looks like the webpage at http://0.0.0.0:1080/ might be having issues or it may have moved permanently to a new web address."
I have tried out clearing browser cache, changed browser security setting to allow unprotected sources, tried both explorer and chrome browser and also tried out this solution for this erro as surgested by microsoft but it didnt work.
i expect the default devmail server page which displays as follows and iam wondering what might be the problem.
Configure your application to send emails via port 1025 and open localhost:1080 in your browser.
https://github.com/maildev/maildev#configure-your-project
If http://localhost:1080 doesnât work, try http://127.0.0.1:1080
I'm trying to switch to Firefox for development but I'm stuck at this error and I have no idea what it could be.
The problem is specifically with our Login endpoint, which sets HttpOnly cookies on successful login. In development this works on both Safari and Chrome, but trying to login on Firefox returns a NS_ERROR_DOM_BAD_URI error.
In development, web is running at http://localhost:3000, the API is on https://localhost:5001.
I assume Firefox is blocking the login because the api and the web are technically on different origins, but I don't understand why it would be doing that for localhost.
Is there a way to disable this error entirely?
On my localhost development environment, when I manually browse to http://localhost it automatically redirects me to https every time.
And I get this error:
When I do the same in chrome, it successfully goes to http.
Is there anyway I can mitigate this or to get https to work on my local dev servers? Any help would be greatly appreciated because until I fix it I can't use safari.
The answer to this is the same as this answer for this Ask Different answer by #Johnathan Elmore:
HSTS Policy is now included in Safari's stored website data, and you can remove localhost data to clear this issue.
command + ,
Privacy -> Manage Website Data...
Search localhost
Click Remove
Change https://localhost to http://localhost in your address bar and click return key.
The trick here is that, at some point, you visited a localhost with an HSTS policy, which means that it will never attempt to visit the HTTP version. This is a great security feature for websites generally, but problematic for local development.
I am trying to test an ASP.NET Web Api locally using IIS Express. When I use Chrome and hit the url (localhost:5000/api/test, for example) the json displays fine, but when using Postman I keep getting unauthorized 401.2 when hitting the same url. The api controller has Anonymous access on the route.
On the error message, one of the likely causes is:
Integrated authentication is enabled and the request was sent through a proxy that changed the authentication headers before they reach the Web server.
Is Postman somehow changing the headers?
[2019 Update]
Got the same issue, I couldn't debug an ASP Core 2.1 API using Postman when running on the local machine using IIS Express. I kept on having "Could not get any response" despite it was working fine on a browser.
Following troubleshooting steps explained here PostmanLabs Github, I noticed into Postman console that this was coming from a certificate issue.
Disabling SSL Verification from Postman Settings > General allowed the request to pass through.
Looks like it's your proxy.
I haven't found the proxy setting in postman. So I deleted postman for Win and installed postman for Chrome. Possibly Postman gets the environment from Chrome.
Anyway the resolution is to use Postman for Chrome instead of Postman for Win.
I have a localhost WebAPI site up with IIS Express (HTTPS). Postman started to respond as expected to GETs and POSTs after I changed (in Postman)
File --> Settings --> Proxy
to: "Use the system proxy"
and turning on: "Respect HTTP_PROXY ...".
I had earlier set up a custom proxy that wasn't working with HTTPS.
I'm trying to figure out why Chrome (26.0.1410.64) and IE10 don't seem to recognize the cookie I set in my response from an ASP.NET Web API controller. Here is the situation:
I have a drop-down menu login form on my page that makes an ajax call to my Web API method (via HTTP POST) and that Web API method returns some JSON data and also sets a cookie in the response (using the HTTP headers). It works perfectly in Firefox and Safari (so, WebKit) but not in Chrome or IE. Chrome and IE appear to completely ignore the cookie that's sent back in the response. I've verified (using Fiddler) that the cookie is sent back on the response so I know it's there - I can't figure out why IE10 and Chrome don't pick it up though.
Any ideas? Does it have something to do with how Chrome and IE10 handle response cookies in ajax requests?
So I figured out the issue, although it's not something I really would like to accept as a solution. I guess I will just have to deal with it and always test the site on my local machine using Firefox.
So here's the issue:
When I run my site locally by running it from Visual Studio and IIS on my local machine, it creates a website at an address like http://localhost:1839/. For some reason, ajax cookies get ignored by IE10 and Chrome when it's "localhost" - but not when it's a real-looking host name or IP Address. So if I edit my host file and create a generic entry like localhost.com and point it at 127.0.0.1:1839 then everything works fine in IE and Chrome (and Firefox still as well).
It's when I use the localhost:1839 address that ajax cookie only works in Firefox.
So what I ended up doing was deploying my website to a different test IIS server (on another machine) that I have a test.mydomain.com entry in my local host file for - that points to the test IIS server's IP address. Now IE, Chrome and Firefox all accept the ajax cookie from this faked "test.mydomain.com" domain.
So for those of you sending cookies back on an ajax request - beware of this "localhost" issue with Chrome and IE.
The Domain on the set cookie is most likely conflicting against using localhost. If you edit your hosts file and add a alias it will make test.mydomain.com point to your local machine:
Within c:\windows\System32\drivers\etc\hosts add the following:
127.0.0.1 test.mydomain.com
Start your webserver within Visual Studio
Close all browsers, then load test.mydomain.com