[modwsgi] Re: Configuring mod_wsgi with Apache

2016-09-23 Thread Roger Wayne
Thanks for the advice, Graham! But I am still a little bit confused though. If you set your application to run on port 8080, shouldn't there be something there when you try to connect to http:localhost:8080? Well at least able to connect to the application running there? I am able to print

Re: [modwsgi] Re: Configuring mod_wsgi with Apache

2016-09-23 Thread Graham Dumpleton
> On 24 Sep 2016, at 9:56 AM, Roger Wayne wrote: > > Thank you. I would have never came to that conclusion. If that is the case, > would you happen to know when referencing the program, what do I actually > refer to? The program itself (the file) or where it is running

Re: [modwsgi] Re: Configuring mod_wsgi with Apache

2016-09-23 Thread Roger Wayne
Thank you. I would have never came to that conclusion. If that is the case, would you happen to know when referencing the program, what do I actually refer to? The program itself (the file) or where it is running on your localhost? I mean this in a way towards using POST requests with AJAX in a

Re: [modwsgi] Re: Configuring mod_wsgi with Apache

2016-09-23 Thread Graham Dumpleton
> On 24 Sep 2016, at 5:28 AM, Roger Wayne wrote: > > I have returned. It seemed like all was working well when I ran into trouble > trying to parse HTML data from my Python script. I just assumed it was maybe > my script or my front-end code that was the problem. In my

Re: [modwsgi] Re: Configuring mod_wsgi with Apache

2016-09-23 Thread Roger Wayne
I apologize. Maybe an example would help clarify. For CGI, when using POST/GET requests, you refer to the actual file itself. xhttp.open("POST","filename.py",true); Is it the same deal with a WSGI application? And thanks for the additional resources. When I get the basics running, I will look

Re: [modwsgi] Re: Configuring mod_wsgi with Apache

2016-09-23 Thread Roger Wayne
Will do. Thanks for all the help again. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to modwsgi+unsubscr...@googlegroups.com. To post to this group, send email to

Re: [modwsgi] Re: Configuring mod_wsgi with Apache

2016-09-23 Thread Graham Dumpleton
How you make web requests depends on the client you are using. Go read those posts and you will leant more about how URLs work and how to address your web application. You will save your own time and ours by learning about it rather than fiddling around trying to make it work by trial and

Re: [modwsgi] Re: Configuring mod_wsgi with Apache

2016-09-23 Thread Graham Dumpleton
> On 24 Sep 2016, at 9:31 AM, Roger Wayne wrote: > > Thanks for the advice, Graham! But I am still a little bit confused though. > If you set your application to run on port 8080, shouldn't there be something > there when you try to connect to http:localhost:8080? Well

Re: [modwsgi] mod wsgi versions

2016-09-23 Thread Graham Dumpleton
I meant to use: http://site1.me http://site2.me in the browser when making the request, not in ServerName. ServerName should be just the hostname. Are their symlinks in the sites-enabled directory to the files in the sites-available directory? Just

[modwsgi] Re: Configuring mod_wsgi with Apache

2016-09-23 Thread Roger Wayne
I have returned. It seemed like all was working well when I ran into trouble trying to parse HTML data from my Python script. I just assumed it was maybe my script or my front-end code that was the problem. In my Python script, I set the running instance of it on port 8080 and when I tried to