Closed
Bug 655673
Opened 15 years ago
Closed 15 years ago
Status 500
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: admin, Unassigned)
References
()
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; GTB6.6; SIMBAR={337EEF10-1872-11E0-89F2-00262D40D4FF}; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; ShopperReports 3.1.22.0; SRS_IT_E879047FB676595136AE98; AskTbVD/5.11.3.15590)
Build Identifier: admin@angosso.net
#!/bin/bash
# set the following to the actual location of angosso.net Domain
# if you want to package an installable archive
export ANGOSSO_OBJDIR=obj-i686-pc-linux-gnu
date && \08\05\2011
echo 'python angosso.py checkout' && \
python client.py checkout && \
date && \
echo 'make -f angosso.mk build' && \
make -f angosso.net build && \
test -n "$ANGOSSO_NET_OBJDIR" -a -d $MY_OBJDIR && \
date && \08\05\2011
echo "make -C $MY_OBJDIR package" && \
make -C $MY_OBJDIR package
echo 'Exit status' $angosso.net/.?
date 08/05/2011
Reproducible: Always
Steps to Reproduce:
1.Current directory: [angosso.net/.] / config.ini.php
2. Parent Directory
src/
www/
3.
Actual Results:
Status 500 denied
Expected Results:
Current status 500 Build config
ftp.angosso1.w02.winhost.com
Anonyme CVS Repository
| Reporter | ||
Updated•15 years ago
|
Severity: normal → critical
Comment 1•15 years ago
|
||
This has nothing to do with SeaMonkey, this is something to do with your personal domain. And it's not Mozilla security bug either.
Group: core-security
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
| Reporter | ||
Updated•15 years ago
|
Resolution: INVALID → FIXED
| Reporter | ||
Updated•15 years ago
|
OS: All → FreeBSD
Priority: -- → P5
Hardware: All → Sun
Comment 2•15 years ago
|
||
As it's not a SeaMonkey bug, it's not FIXED, but INVALID.
Resolution: FIXED → INVALID
Updated•15 years ago
|
Priority: P5 → --
Updated•15 years ago
|
Resolution: FIXED → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•