I am trying to use the Dropbox drop-ins in one of my projects. It is a web application that should be able to be run locally without a web server. I am using the Dropbox chooser, but it gives an error if it is not running on a web server. It says "invalid origin". Is it possible to get rid of this error without using a local web server to run the application?
You'll probably need to run a local server. Each domain you serve your page from has to be entered in the App console. "localhost" or "127.0.0.1" will work, but those require you to actually run a local web server. (It doesn't have to be a complicated web server... python -m SimpleHTTPServer would work.)
Related
I am publishing my ASP.NET Core 2.2 to a local location, then zipping it and trying to run on another machine. The other machine when launching does not show listening on HTTPS, only HTTP.
This is making the app not work. Locally on my dev machine I get both endpoints. I understand that I have to possibly use dotnet dev-certs https --trust or similar command but since my build is self-contained I really do not want to install the .NET Core SDK on every machine I run this on just to get that command.
How can I make my app run with endpoint on the other machine with the least hassle?
Update:
The following message is also shown in the launch console window:
warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3]
Failed to determine the https port for redirect.
I've been searching Google and StackOverflow about this for several hours now, and nothing seems to work.
I created a Web API server in ASP.NET Core and verified it works locally.
I created a new EC2 VM to host the Web API. I copied all the binaries for the API up to EC2, and started the server from the command line.
I have made sure that the required EC2 security group exists and that the correct TCP port is open for Input in the security group.
I have added an appropriate firewall rule to Windows firewall.
NETSTAT -Q shows that the server is working and that the port is in LISTENING mode.
I get the public IP address for my EC2 VM and go back to my local machine.
I use POSTMAN to submit POST requests to the EC2-based server.
POSTMAN returns an error: "There was an error connecting to ...."
So I'm at a loss as to what to do next. Have I missed some EC2 configuration? Is there something else I have to do to the ASP.NET Core WebAPI code?
Well I am not an expert on Apache or any web server, I have recently finished my first web app, so I have rsyncd code to web server /HTML.
The web app is python flask based uses wsgi module to load.
I do not have control over Apache as it's taken care by systems department.
So I cannot test myself in office. I just want to know if we upload updated/modified code to the host machine running apache web server, will it pick up changes or we need to restart the Apache web server?
I have created a server in liberty and installed IBM Worklight in it.
Everything was working fine till I protect the console.
After protecting the IBM Worklight console the authentication is asked
twice.
First Login Screen with URL localhost:9080
After Login Successful.Again the login is being asked with the hostmachines URL 192.168.10.16:9080
My questions are
Why login appears twice?
Why my hostmachine ip is being revealed?
You are accessing the console with address localhost, whereas in your code you are either using publicWorklightHosname=192.168.10.16 or while building you are using build for remote machine and then putting in IP of the server.
Here is what you need to do:
Make sure a DNS entry of the hostname is present in the server and client machine
Change the publicWorklightHostname property in worklight.properties file to a proper address eg
mymachine.mydomain.com
while building for Remote Server, use the same address as above i.e. mymachine.mydomain.com
redeploy the new war file
Worked perfectly for me.
P.S> I believe you are using local machine, in this case also you can use the machine name in worklight.properties file and make sure that the address you are using is same as the one you used to build. Nonetheless, it doesn;t matter in production or application deployment.
I have been trying to setup an Apache web server along with a Tomcat6 web server, using SSL/HTTPS. On my Apache web server the SSL is working correctly, and I can access the web pages it serves up using SSL/HTTPS, but I am having a problem accessing the web apps on the Tomcat server using SSL/HTTPS. The new setup is on a Centos 6 machine, and I have a similar setup on a Fedora 13 machine.
I have compared all the files that I can think of between the two machines, but can not get to the web apps using HTTPS. When I try I get a "Not Found" error. I can access the web apps if I use just HTTP.
Can anyone point me to where my problem might be?
Thank you