Direkt zum Hauptbereich

Python and Access-Control-Allow-Origin

Ok, here is something that probably happens a lot:

You are trying to do some .js (if not you should get started), and write some code in your favorite ide, save it, load it in your favorite browser and everything is ok. You are a good developer and start making packages and loading your files when you need them: lazy. You don't want to overdo things, and manage to put stuff into a bunch of .js and .html. You load them into your browser and BAM:

Access-Control-Allow-Origin  
Failed to load resource: Resource failed to load  
So now you are all WTF, right? You Google (some would Bing) it and sure enough, what you were thinking is the ugly true and by now you get angry as a bird. Why? Ok, for those that didn't know there is a thing called Same Origin Policy, that forbids you from loading stuff across different domains and bla bla bla... So what does it has to do we you? You sure enough are not trying do load across domains, your are loading a file... you may think, but no. Your file is from a different origin than your loaded page. At this point nearly every post tells you to run a server or allow file access in your browser. The latter is probably a very bad idea if you do actually browse occasionally through the web. So a server.. right... you have lots of them because you are a developer, but you have to configure a lot of stuff to make them point to the right directory.

(Meh.)

But then there is this other way using python:

$ cd WebPageProject/
$ python -m SimpleHTTPServer
Serving HTTP on 0.0.0.0 port 8000 ...
Simple indeed and beautiful.

Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

ThreadLocal as an Enum - I'm not afraid to admit it!

Well, as disturbing as it might be, I am not afraid to at least admit it: I did not know about the elegance of the following construct: public enum TLData { INSTANCE; private final ThreadLocal< String > myData = new ThreadLocal< String >(); public String getMyData() { return myData.get(); } public void setMyData( final String myData) { this .myData.set(myData); } } Since you are using an Enum, nobody can create new members from outside, you don't have to care about privatizing any methods and you can access it as easy as: public class myClass { public void myMethod() { /** * setting the data */ TLData.INSTANCE.setMyData( "some data" ); /** * getting the data */ String myData = TLData.INSTANCE.getMyData(); } } Isn't that fancy? I had to admit I never thought of it myself. A colleague of mine had to put it under my nose.
Kommentar veröffentlichen
Next »

JUnit testing services and clients with javax.xml.ws.Endpoint

Following situation: you have written some generic stub to use in your projects that creates a client for a service. Your client is smart and does some magic for connections (proxy, cache or other kind of magic). Or maybe you just have written a service for that matter. Anyway, you now want to test it. Unit testing the functionality of your methods is a must. But you still want to reach 100% coverage and need to test the service as it would run in real life. Then you can use the javax.xml.ws.Endpoint class. If you prefer figuring it out yourself, you can find the code (as a project for netbeans) -- here -- To follow the code examples as html click   --here-- So here is how you do it: If you've coded nothing fancy, then you probably have a class like this: This is a generic client for opening connections to services. It gives you back a port of the type of your service where you can call your operation as a method of the port. It is very convenient if you h
Kommentar veröffentlichen
Next »