<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>If this is a static file, i.e. a file that you upload to the
server and is served as-is, then you do not need anything beyond
nginx. nginx does a great job at serving static content.<br>
</p>
<p><br>
</p>
<div class="moz-signature">
<p>Igal Sapir
<br>
Lucee Core Developer
<br>
<a href="http://lucee.org/">Lucee.org</a></p>
</div>
<div class="moz-cite-prefix">On 3/11/2017 9:08 PM, Ran Shalit wrote:<br>
</div>
<blockquote
cite="mid:CAJ2oMhJGd_xzfh3EnZ=5ZdCZ5jKTwsKSbNfYZco1XVXweqShCw@mail.gmail.com"
type="cite">
<p dir="ltr"><br>
On Mar 11, 2017 9:04 PM, "Igal @ Lucee.org" <<a
moz-do-not-send="true" href="mailto:igal@lucee.org">igal@lucee.org</a>>
wrote:<br>
><br>
> Ran,<br>
><br>
> You would probably want to use an Application Server behind
the Web Server (nginx). Then you would use the nginx to proxy
the request to the application server, where you can write code
in the language that the application server supports (for
example, I use Lucee as an application server, but many people
use PHP or JSP or a bunch of other technologies).<br>
><br>
> In the application server you can do whatever you want with
the request, e.g. read request parameters and build an XML
document on the fly, and send it back to nginx which will send
it back to the client.</p>
<p dir="ltr">Hi, <br>
In case we just want to save xml file(like a binary file) and
later read it, Is there any need for application in server or is
it only nginx server required for such reuirement?<br>
Thank you,<br>
Ran</p>
<p dir="ltr">><br>
> nginx is a web server, similar in function to apache httpd
or IIS, but much better in my opinion (and in the opinion of
most users on this list, I would think), but if you want to
serve dynamic content then you should have an application server
behind it.<br>
><br>
> HTH,<br>
><br>
> Igal Sapir <br>
> Lucee Core Developer <br>
> Lucee.org<br>
><br>
> On 3/10/2017 11:07 PM, Ran Shalit wrote:<br>
>><br>
>> On Sat, Mar 11, 2017 at 12:19 AM, Jeff Dyke <<a
moz-do-not-send="true" href="mailto:jeff.dyke@gmail.com">jeff.dyke@gmail.com</a>>
wrote:<br>
>>><br>
>>> what do you want it to do? if you're talking nginx
without any application<br>
>>> backend you could do a lot with some lua locations,
or you're going to pass<br>
>>> that request to another process, or serve a static
(xml) file from the file<br>
>>> system.<br>
>><br>
>> Hi Jeff,<br>
>><br>
>> Thank you very much.<br>
>> I have requirement that application should "support
webserver which<br>
>> includes xml and save xml file to filesystem"<br>
>> Does it mean that it actually should " serve a static
(xml) file from<br>
>> the file" (the second option you mentioned).<br>
>> If yes - can you give some hints about it or where to
read further about it ?<br>
>><br>
>> Does it mean it just save and retrieve file parsing it
to other<br>
>> commands ? (I have read somewhere that uploading a file
parse the<br>
>> file, so I am a bit confused here)<br>
>><br>
>> I am new with nginx, still learning it.<br>
>><br>
>> Many thanks,<br>
>> Ran<br>
>><br>
>> Nginx does support XML just fine, its all a matter of
what you want<br>
>>><br>
>>> your application to do.<br>
>>><br>
>>> On Fri, Mar 10, 2017 at 12:01 PM, Ran Shalit <<a
moz-do-not-send="true" href="mailto:ranshalit@gmail.com">ranshalit@gmail.com</a>>
wrote:<br>
>>>><br>
>>>> Hello,<br>
>>>><br>
>>>> I am new with web servers and nginx.<br>
>>>> I would like to ask if nginx support xml , and
what does it mean to<br>
>>>> upload xml to web server ?<br>
>>>> Does it just keep the xml as file in some
directory , or does it do<br>
>>>> parse the xml file and do some actions ?<br>
>>>><br>
>>>> Thank you,<br>
>>>> Ran<br>
>>>> _______________________________________________<br>
>>>> nginx mailing list<br>
>>>> <a moz-do-not-send="true"
href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
>>>> <a moz-do-not-send="true"
href="http://mailman.nginx.org/mailman/listinfo/nginx">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> nginx mailing list<br>
>>> <a moz-do-not-send="true"
href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
>>> <a moz-do-not-send="true"
href="http://mailman.nginx.org/mailman/listinfo/nginx">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
>><br>
>> _______________________________________________<br>
>> nginx mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
>> <a moz-do-not-send="true"
href="http://mailman.nginx.org/mailman/listinfo/nginx">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> nginx mailing list<br>
> <a moz-do-not-send="true" href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
> <a moz-do-not-send="true"
href="http://mailman.nginx.org/mailman/listinfo/nginx">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
nginx mailing list
<a class="moz-txt-link-abbreviated" href="mailto:nginx@nginx.org">nginx@nginx.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.nginx.org/mailman/listinfo/nginx">http://mailman.nginx.org/mailman/listinfo/nginx</a></pre>
</blockquote>
<br>
</body>
</html>