Tag Info

New answers tagged


If you want to share a folder or a fiel within your network you can use the folder sharing option. Here is a tutorial for windows 7. For Linux look for samba


If you want to see it in a web browser via the HTTP protocol, then you need to install an HTTP server (e.g. IIS). If you want to access the file to work with it, maybe in something like Word or Photoshop, then you would only need to turn on Windows file sharing.


You need some sort of web server to host things via http. It could be a short script, but usually apache or nginx is easier to get going for hosting a few static files.


The HTTP protocol allows the client application (usually a web browser) to create HTTP requests containing the name of the web site it wants to contact; this allows multiple web sites to coexist on the same IP address and port. All web servers can be configured to serve different contents based on the name of the web site the client is asking for; also, ...


This is by design. According to RFC 2396: A URI reference that does not contain a URI is a reference to the current document. In other words, an empty URI reference within a document is interpreted as a reference to the start of that document, and a reference containing only a fragment identifier is a reference to the identified ...


OMG! Im so stupid. I finally found the error here. The regEx is just fine and working properly. Its the grep option '-L' that is totally crap. Its supposed to be '-l' to just return the path and filenames that matches. grep -l -R -e 'https://hostname/' /srv/www/htdocs/intranet/data/pages/*.txt | xargs -n1 sed -i.bak ...


I recommend to debug on one selected file: sed 's|something|replacement|g' a_file.txt to see what happens. When your regular expression is debugged, you can simplify your command like this: shopt -s globstar sed -i.bak 's|https://hostname/|https://hostname.fq.dn|g' /srv/www/htdocs/intranet/data/pages/{,**/}*.txt There's no need for the grep and xargs. ...

Top 50 recent answers are included