The text for the HTTP status code is set by the server. In PHP for example
you can set it like this:
header("HTTP/1.1 200 Everything's fine");
The important part for the browser is the status code, the text is just for
human readability. For 302 the official text is "Found". For a list of all
status codes see RFC 7231 <https://tools.ietf.org/html/rfc7231#section-6.1>.
Sebastian
On Monday, November 10, 2014 10:43:45 PM UTC+1, Josh K wrote:
>
> Hello,
> I've been a user of Firebug for a while and love it! I just ran into
> something I'm trying to figure out. The situation is this: There is a
> corporate page (that I do not manage) that contains links to various
> internal services. I am managing one of those services and am trying to
> diagnose an issue with users failing to go from the main page to my
> service. The connection is redirected twice in the main server before it
> is sent to my service. I'm using Firebug to watch the connection redirects
> and am wondering why I am seeing Firebug show different types of 302's.
> There is a redirect in my service to test some new functionality for some
> users which is the reason for the third 302. Here's what I see in the Net
> panel (just URL and Status columns for simplicity):
>
> URL Status
> --------------------------------------------------------------
> GET url1 302 Redirect
> GET url2.aspx 302 Found
> GET myservice 302 Moved Temporarily ....
> GET myservice 200 OK
> ....
>
> I am wondering if there is documentation describing what Firebug uses to
> determine the qualifier for each 302? It seems that each 302 should be a
> temporary move, but Firebug is making me think there is more information it
> is using to populate the Net panel that may be helpful in diagnosing my
> issue.
>
> Any insight would be appreciated!
>
> Thanks!
>
--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit
https://groups.google.com/d/msgid/firebug/5c4b7a2a-09d7-4c55-91cc-6d1eaf7eae23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
