Can someone shed some light what these two regex expresssions solve to:

1) ^/(tv\/[^\/]*\/)$
2) ^/tv\/[^\/]\/(.)

How about

man 7 regex

?

As you can see from previous answers, if you don't do any work then no one else is inclined to either.

Maybe tell us either which part you do not understand or what you think it equals or what parts equal?

Then we can assist with either incorrect assumptions or educate on plain wrong solutions.

i know i was a bit short and dry in my original post but my apache config is driving me crazy and the regex is the least of my problems atm. anyways, i found the captioned regex expressions and i am trying to make sense out of them to get a complete picture of the infrastructure. These are used within the ProxyPassMatch directive:

1)^/(tv\/[^\/]*\/)$

Match something like this: mydomain.com/tv/anything_but_not_slash/

2) ^/tv\/[^\/]\/(.)

Match something like this: mydomain.com/tv/a

I really hate asking questions i can find answers myself...coming here and being referred to manual pages is really insulting. but anyways, kids.

Really ? As I have established many times already, people simply do not read. I.e. quite often the needed info is the manpage, sometimes even in the first-second line of description, but people still ask questions instead of reading.

I even sometimes request such askers to parse English sentences from the manpages in question in order to show them that the answer is indeed there, but they didn't read it.

My standard question in such cases is: "What is the very first thing you didn't understand ?".

In fact, when I realize I do not understand something in the text I am reading, I ask myself the same question - giving a concrete answer really helps to move forward.

So, what is the very first thing you didn't understand in the manpage ?

http://catb.org/esr/faqs/smart-questions.html#before
http://catb.org/esr/faqs/smart-questions.html#beprecise
http://catb.org/esr/faqs/smart-questions.html#rtfm



String starts with literal "/tv/". Then has 0 or more characters that are not \ or /*. String ends with a literal /. The substring starting with "tv" and ending with / is captured.
String starts with literal "/tv/". Then has one character that is not \ or /. Then has a literal /. Then, one character is captured. After that one character we don't care what's there and don't even try to match it.

* not sure if [^\/] means "not /" or "not \ or /" since it's in a [] block. I should go back to the manual.

It's odd that you're escaping some /s with \s and some of them you aren't. You don't seem to be using // as regex delimiters (regexes are often delineated by /s, ie "$foo =~ /regexhere/;") so it's not clear whether you need to escape them or not.

Yes to me it looks really odd, and since I didn't do the regex, but merely interpreting it in an apache context, I was doubting my regex knowledge and hence came here. In the future I would like to use some tools which help me simulate regex.

Anyways thanks for confirming my thoughts..

Is this meant to be a conundrum?

1. You hate asking questions when you can find the answers yourself .... then why ask??

2. You feel insulted because you are directed to a manual page or reference, so your solution is just to tell everyone answers and not educate .... interesting concept

3. Personally I find it insulting to be called a 'kid' when I am 40+ years of age

If you don't want to be educated or don't like the answers, maybe you should learn how to ask a question!!

The link at the bottom of AlucardZero's signature should be your starting point.