Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 2 years ago.
Improve this question
I've tried all of the steps in the instructions, but always get an error at #5 when it is supposed to redirect to google.com.
https://developers.google.com/nest/device-access/authorize#link_your_account
The error:
Authorization Error
Error 400: redirect_uri_mismatch
The redirect URI in the request, https://www.google.com, does not match the ones authorized for the OAuth client. To update the authorized redirect URIs, visit: https://console.developers.google.com/apis/credentials/oauthclient/${your_client_id}?project=${your_project_number}
I've ensured I have the right numbers- without spaces in the url and have put it in notepad and deleted all of the returns so it is one line of text.
any ideas?
What do you have listed in the Authorized Redirect URIs for your OAuth client in GCP, and what is the exact PCM URL you used? You shouldn't get this error if the redirect_uri and client_id parameters in the PCM URL matches what you have in GCP for the client.
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 19 hours ago.
Improve this question
I am getting a CORS issue saying a header is missing, but the header is present in both server's code.
Here is what I am trying to do:
POST request from frontend to nodeServer1, then inside the endpoint I make a POST request to nodeServer2
And then a response is sent back to the front end.
My Access-Control-Allow-Origin policy is "*" for nodeServer1, and is "[nodeServer1URL]", "[frontendURL]" for nodeServer2.
When I make another request from the frontend to nodeServer1, I am not getting any issues. But for the request I'm trying to get here is the error:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at "[nodeServer1EndPointURL]". (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.
nodeServer1 executes whatever is in the endpoint as expected. When I test locally the nodeServer2 endpoint it works as well, so it has to be CORS.
So the issue is most definitely with nodeServer2's policy, which is apparently missing. Even if I set the policy of nodeServer2 to "*" it fails with the same error. I don't know why.
Not sure why is the remote resource my full endpoint URL.
So my question is, how can I fix this CORS issue?
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 months ago.
Improve this question
I know thats not the kind of question that are commonly asked in here, but I don't know where to ask instead.
I want to setup DynDNS with my FritzBox 6600 Cable, but i always got an 500 - notfqdn (not full qualified domain name) Error. (I know FritzBox is not the best solution avaiable... but this is what i have to work with).
According to this guide i set up the DynDNS config in the FritzBox and used the username and password from the configured DynDNS and the update url domains.google.com/nic/update with the dyndns domain. The config in the FritzBox looks like the following:
Update-URL: domains.google.com/nic/update
Domainname (Domain-Name): something.my-domain.de
Benutzername (Username): my_username
Kennwort (Password): my_password
I don't know what's the problem. Some testing with other configuration shows that a random user and password give the same 500 error.
Do anybody know how the request of the FritzBox looks like and how the parameters are parsed?
According to the FRITZ!Box help page you can use pre-defined placeholders inside the Update URL which will be filled with the corresponding information.
So in the case of Google Domains the API expects a request URL in the following form:
https://username:password#domains.google.com/nic/update?hostname=subdomain.yourdomain.com&myip=1.2.3.4
In your FRITZ!Box DynDNS configuration you have to replace the variables in the Google Domains API URL by the corresponding placeholders from the FRITZ!Box documentation, which will look something like this:
https://<username>:<pass>#domains.google.com/nic/update?hostname=<domain>&myip=<ipaddr>
Note that the URL might be different depending on your FRITZ!Box type.
For further information check out the Google Domains help page Learn about Dynamic DNS
(especially the section "Use the API to update your Dynamic DNS record") and the help page of your FRITZ!Box, which may be accessed using the question mark icon in the top right of the DynDNS configuration page. (Help page for FRITZ!Box 7590)
You need to change the URL into following syntax
https://username:password#domains.google.com/nic/update?hostname=subdomain.yourdomain.com
Use the userdefined DynDNS provider.
Update-URL: https://domains.google.com/nic/update?hostname=mydyndns.yourdomain.com
Domainname: mydyndns.yourdomain.com
Username: generated username from Google Domains
Password: generated password from Google Domains
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
I've noticed a problem today when accessing our https:// azurewebsites.net websites in Firefox.
The following sites (and I suspect any https azurewebsites.net site) fail on Firefox :
https://easytees.azurewebsites.net/
https://easyfurniture.azurewebsites.net/
https://hello.azurewebsites.net/ (not one of ours)
returning :
Secure Connection Failed
An error occurred during a connection to easyfurniture.azurewebsites.net. Invalid OCSP signing certificate in OCSP response. Error code: SEC_ERROR_OCSP_INVALID_SIGNING_CERT
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
The sites work fine in Chrome, Safari, and Tor browsers.
Why do https://*.azurewebsites.net fail in this way in Firefox?
Microsoft has an active issue with this. Try going to https://microsoft.com or https://portal.azure.com in Firefox and you see the same behavior.
Open tickets:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12163379/
https://developercommunity.visualstudio.com/content/problem/62465/receiving-a-sec-error-ocsp-invalid-signing-cert-wh.html
Expired certificate: https://twitter.com/vcsjones/status/869033508114661376
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
In IIS7.5, I have a URL Rewrite rule that redirects http requests to https. If I check "Require SSL", I get a 403 Unauthorized instead of a redirect, which makes sense.
Is there a way to use them together? Would there even be a benefit? I'm assuming no since every http request would be redirected, but I'm checking here in case I'm wrong.
Is this secure?
The 2 options work a very different way.
If you use the Require SSL option, every single page of your website has to be accessed by HTTPS and it means that (as you have seen it), if you forget the HTTPS and try to access with HTTP, you will have a 403 Unauthorized.
If you use the URL Rewrite Module, you can setup some pages or your whole website to be redirected to HTTPS (and some part back to HTTP if needed), and if a user forgets the HTTPS and hits the HTTP, he/she will be redirected to the HTTPS url.
As of having them to work together, there is a solution, but I don't really see the point:
[...] you will need to disable “Require SSL” checkbox for the web
site. If you do not want to do that, then you can create two web sites
in IIS – one with http binding and another with https binding – and
then add this rule to the web.config file of the site with http
binding.
http://blogs.iis.net/ruslany/archive/2009/04/08/10-url-rewriting-tips-and-tricks.aspx
(Section 4. Redirect to HTTPS)
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I have an application built with CodeIgniter that a 3rd party service (an email service provider) is making http requests containing POST data to when certain events occur. The problem is, the url that this 3rd party service is making the requests to is not fully modifiable by me, specifically, it make its requests to a file named w_4.php at the domain and directory that I specify.
Instead of having this separate file outside of the CodeIgnitier stack, I would like to, using .htaccess, rewrite all the requests made for this file to a controller within my codeigniter application, i.e. api/my_controller/my_method. But I need the POST data in the request intact, so I would think a redirect could not be used.
I tried something like this in my .htaccess:
RewriteCond $1 (w_4\.php)
RewriteRule ^(.*)$ index.php/api/my_controller/my_method
While the request does get routed to codeigniter, I just get a 404 even though that controller/route does exist.
The answer is to use the P proxy flag in the RewriteRule. As detailed here https://stackoverflow.com/a/359224/192694, the flag indicates that the request should be passed off to the proxy module intact, including its POST data.
For more info: http://httpd.apache.org/docs/2.2/rewrite/flags.html#flag_p